From: Eric Sherman <hyperbolist@gmail.com>
To: Michael Stapelberg <michael+sup@stapelberg.de>
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
Date: Fri, 19 Mar 2010 16:40:46 -0400 [thread overview]
Message-ID: <1269029869-sup-4474@changeling.local> (raw)
In-Reply-To: <1269027951-sup-4565@midna.zekjur.net>
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
next prev parent reply other threads:[~2010-03-19 20:46 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-19 15:36 Michael Stapelberg
2010-03-19 19:17 ` Mark Alexander
2010-03-19 19:27 ` Michael Stapelberg
2010-03-19 19:35 ` Ben Walton
2010-03-19 19:47 ` Michael Stapelberg
2010-03-19 20:05 ` Ben Walton
2010-03-19 21:02 ` Rich Lane
2010-03-19 20:35 ` Mark Alexander
2010-03-19 21:17 ` Rich Lane
2010-03-19 19:34 ` Eric Sherman
2010-03-19 19:46 ` Michael Stapelberg
2010-03-19 20:40 ` Eric Sherman [this message]
2010-03-19 21:04 ` Mark Alexander
2010-03-20 2:23 ` Mark Alexander
2010-03-22 11:30 ` Michael Stapelberg
2010-03-22 16:25 ` Ben Walton
2010-03-25 6:25 ` Tero Tilus
2010-03-22 17:00 ` Rich Lane
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1269029869-sup-4474@changeling.local \
--to=hyperbolist@gmail.com \
--cc=michael+sup@stapelberg.de \
--cc=sup-devel@rubyforge.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox