David Carter wrote:
On Mon, 6 Aug 2007, Ken Murchison wrote:
My gut is to use the 'replace' patch. I'm not comfortable with the 21
byte scenario.
I agree that 21 bytes is likely to be a pain to maintain long term.
If we need a UUID schema version, we can always use a new MINOR_VERSION.
This sounds like a plan. For the time being I am using the first 11
bytes of message MD5 sums on my Cyrus 2.3 systems, just like Fastmail.
It would be useful to have a migration route to full 20 byte SHA1 UUIDs.
Zero padding existing schema 1 and schema 2 UUIDs is probably good enough.
I'm going to leave this stuff out of 2.3.9 and add it in for 2.3.10.
--
Kenneth Murchison
Systems Programmer
Project Cyrus Developer/Maintainer
Carnegie Mellon University
