From mboxrd@z Thu Jan  1 00:00:00 1970
Received: by 10.86.87.8 with SMTP id k8cs24250fgb;
        Fri, 19 Mar 2010 12:46:49 -0700 (PDT)
Received: by 10.229.217.206 with SMTP id hn14mr832908qcb.70.1269028008793;
        Fri, 19 Mar 2010 12:46:48 -0700 (PDT)
Return-Path: <sup-devel-bounces@rubyforge.org>
Received: from rubyforge.org (rubyforge.org [205.234.109.19])
        by mx.google.com with ESMTP id 38si2981191qyk.59.2010.03.19.12.46.48;
        Fri, 19 Mar 2010 12:46:48 -0700 (PDT)
Received-SPF: pass (google.com: domain of sup-devel-bounces@rubyforge.org designates 205.234.109.19 as permitted sender) client-ip=205.234.109.19;
Authentication-Results: mx.google.com; spf=pass (google.com: domain of sup-devel-bounces@rubyforge.org designates 205.234.109.19 as permitted sender) smtp.mail=sup-devel-bounces@rubyforge.org
Received: from rubyforge.org (rubyforge.org [127.0.0.1])
	by rubyforge.org (Postfix) with ESMTP id 3ADD018582EC;
	Fri, 19 Mar 2010 15:46:48 -0400 (EDT)
Received: from twice-irc.de (mx2.twice-irc.de [79.140.35.195])
	by rubyforge.org (Postfix) with ESMTP id 1EF4C1858289
	for <sup-devel@rubyforge.org>; Fri, 19 Mar 2010 15:46:46 -0400 (EDT)
Received: from midna.zekjur.net (midna.zekjur.net
	[IPv6:2001:4d88:1008:4242:21c:c0ff:fe7e:4776])
	by twice-irc.de (Postfix) with ESMTPSA id 644A01665C5;
	Fri, 19 Mar 2010 20:46:45 +0100 (CET)
Received: by midna.zekjur.net (Postfix, from userid 101)
	id A9F8924019; Fri, 19 Mar 2010 20:46:29 +0100 (CET)
From: Michael Stapelberg <michael+sup@stapelberg.de>
To: Eric Sherman <hyperbolist@gmail.com>
In-reply-to: <1269026805-sup-2720@changeling.local>
References: <1269012878-sup-691@midna.zekjur.net> <1269026068-sup-6868@r61>
	<1269026805-sup-2720@changeling.local>
Date: Fri, 19 Mar 2010 20:46:29 +0100
Message-Id: <1269027951-sup-4565@midna.zekjur.net>
User-Agent: Sup/git
Cc: sup-devel <sup-devel@rubyforge.org>
Subject: Re: [sup-devel] [PATCH 2/2] Use nanosecond resolution of mtime for
	generating the unique id for each message
X-BeenThere: sup-devel@rubyforge.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: Sup developer discussion <sup-devel@rubyforge.org>
List-Id: Sup developer discussion <sup-devel.rubyforge.org>
List-Unsubscribe: <http://rubyforge.org/mailman/options/sup-devel>,
	<mailto:sup-devel-request@rubyforge.org?subject=unsubscribe>
List-Archive: <http://rubyforge.org/pipermail/sup-devel>
List-Post: <mailto:sup-devel@rubyforge.org>
List-Help: <mailto:sup-devel-request@rubyforge.org?subject=help>
List-Subscribe: <http://rubyforge.org/mailman/listinfo/sup-devel>,
	<mailto:sup-devel-request@rubyforge.org?subject=subscribe>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: sup-devel-bounces@rubyforge.org
Errors-To: sup-devel-bounces@rubyforge.org

Hi Eric,

Excerpts from Eric Sherman's message of 2010-03-19 20:34:32 +0100:
> Would inserting an SHA1 into the id solve these problems, or does it just 
> introduce more problems?
The latter. The ID needs to be linear, not only unique.

Best regards,
Michael
_______________________________________________
Sup-devel mailing list
Sup-devel@rubyforge.org
http://rubyforge.org/mailman/listinfo/sup-devel