From: erik quanstrom <quanstro@quanstro.net>
To: 9fans@9fans.net
Subject: Re: [9fans] [plan9mod] Query regarding venti scores
Date: Fri, 6 Feb 2009 10:28:41 -0500 [thread overview]
Message-ID: <80b6d427d11267d6311d222fee1b5af1@quanstro.net> (raw)
In-Reply-To: <509071940902060610p44067dfaue4a0f3ede5fbb5d9@mail.gmail.com>
> that doesn't directly address their suitability as UUIDs. it seems
> like an odd choice to me (certainly it's an expensive way of
> generating them), although i guess it depends what your application
> is.
sha-1 is a standard uuid format. since a uuid is 16 bytes and
sha-1 is 20, there should be plenty of room in there. here's the
fully legal url:
http://en.wikipedia.org/wiki/UUID#Version_5_.28SHA-1_hash.29
- erik
prev parent reply other threads:[~2009-02-06 15:28 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-06 9:49 anoop.anoop
2009-02-06 10:17 ` 23hiro
2009-02-06 14:10 ` Anthony Sorace
2009-02-06 15:28 ` erik quanstrom [this message]
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=80b6d427d11267d6311d222fee1b5af1@quanstro.net \
--to=quanstro@quanstro.net \
--cc=9fans@9fans.net \
/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;
as well as URLs for NNTP newsgroup(s).