From mboxrd@z Thu Jan 1 00:00:00 1970 Received: by 10.86.87.8 with SMTP id k8cs26030fgb; Fri, 19 Mar 2010 13:46:33 -0700 (PDT) Received: by 10.229.191.75 with SMTP id dl11mr4557069qcb.16.1269031590527; Fri, 19 Mar 2010 13:46:30 -0700 (PDT) Return-Path: Received: from rubyforge.org (rubyforge.org [205.234.109.19]) by mx.google.com with ESMTP id 42si2849720qyk.75.2010.03.19.13.46.30; Fri, 19 Mar 2010 13:46:30 -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; dkim=neutral (body hash did not verify) header.i=@gmail.com Received: from rubyforge.org (rubyforge.org [127.0.0.1]) by rubyforge.org (Postfix) with ESMTP id E289818582CB; Fri, 19 Mar 2010 16:46:29 -0400 (EDT) Received: from qw-out-2122.google.com (qw-out-2122.google.com [74.125.92.24]) by rubyforge.org (Postfix) with ESMTP id 674A318582D8 for ; Fri, 19 Mar 2010 16:40:50 -0400 (EDT) Received: by qw-out-2122.google.com with SMTP id 5so374946qwi.29 for ; Fri, 19 Mar 2010 13:40:50 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:content-type:cc:subject:from :to:in-reply-to:references:date:message-id:user-agent :content-transfer-encoding; bh=LX3/wciFQf1kVayD+pcQFtnkj2b62SsuUYWZQdAgx/E=; b=OaoGrmv73hO1fJos743xHz2XMesIzu4/PBt+NLMnKud79BZ5SUxyA8B4dDwqhtNwbv j9aHdNas0lvXxcmXxxcPjcJWinPUOtVxrvA1DHG0RiWxq/DY4UHdWGx2sSmMTlM9dWYC oR5g7wwP28+HS5m9SfwsQ270OGbYNE0zeKRyc= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=content-type:cc:subject:from:to:in-reply-to:references:date :message-id:user-agent:content-transfer-encoding; b=f+PvQJr7u53e0qOnrB1VkFHtxeSNqMWfFF/0Q/i53K92lXs/lEsPYipW/18A46yqUY m9Iis2ohvZiI0EfJNLUfTJbgl6oS1TwIfKvDZ2hqy/qqr3ClYqJc8wfSlv8c8txR+1ZH 1tNDSXmVUDp8eDAjwcnZuDmnkPsW/Hb88US6s= Received: by 10.229.44.5 with SMTP id y5mr5084862qce.11.1269031249077; Fri, 19 Mar 2010 13:40:49 -0700 (PDT) Received: from localhost (c-76-98-96-154.hsd1.nj.comcast.net [76.98.96.154]) by mx.google.com with ESMTPS id 21sm485146iwn.15.2010.03.19.13.40.48 (version=TLSv1/SSLv3 cipher=RC4-MD5); Fri, 19 Mar 2010 13:40:48 -0700 (PDT) From: Eric Sherman To: Michael Stapelberg In-reply-to: <1269027951-sup-4565@midna.zekjur.net> References: <1269012878-sup-691@midna.zekjur.net> <1269026068-sup-6868@r61> <1269026805-sup-2720@changeling.local> <1269027951-sup-4565@midna.zekjur.net> Date: Fri, 19 Mar 2010 16:40:46 -0400 Message-Id: <1269029869-sup-4474@changeling.local> User-Agent: Sup/git Cc: sup-devel 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 List-Id: Sup developer discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-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 Excerpts from Michael Stapelberg's message of Fri Mar 19 15:46:29 -0400 2010: > 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. Oh I see. Is it fair to say that if a set of messages are can only be disambiguated by adding nanosecond precision to their timestamps, the ordering across such a set may as well be arbitrary? In looking at make_id, it seems like we should be able to simply append more numeric noise at the end of the id. The file size is already appended to the mtime, potentially making the ordering arbitrary for equivalent mtimes. Would appending x-digits of numeric noise, probably derived from SHA1, be suitable? _______________________________________________ Sup-devel mailing list Sup-devel@rubyforge.org http://rubyforge.org/mailman/listinfo/sup-devel