On Wed, 2007-08-29 at 10:14 -0700, David Sparks wrote: > A UUID is preferable to the other solutions because you can condense it > down to 128 bits of binary data ... and put it in a database. :)
HiRes::Timer is 64 bits ... leaving 64 bits for the server tag. > > The other solutions are not as database friendly. It seems to me if > we're trying to solve the problem of guaranteeing unique transaction ids > for extremely high volume sites, then we should make sure that the > transaction id itself is high volume friendly. > > Cheers -- --gh
