I don't know about the specifics of the algorithm in question, but as an
example Java's "java.util.Random" random number generator is only based on
the current time when the generator object is created. So I'm assuming in
the ID creation algorithm that unless you are creating a new random number
generator each time you generate an ID, you are not implicitly including
the timestamp as well - hence the need for explicit inclusion.
-David
At 02:09 PM 9/7/01 -0400, Scott Stirling wrote:
>This was great, thanks for the reference. I've been reading some of the
>other chapters too.
>
>A question & suggestion on the Primary Key chapter:
>
>1. Why is the current-time in ms part of the UUID? Since the random string
>at the end is based off the current time, wouldn't that be enough to ensure
>"down to" and "within an object" within a ms? I don't doubt there's good
>reason for it (maybe for substringing and comparing the times?) that I'm
>overlooking. But it could certainly shorten the id string to leave it off.
>Just curious -- is it just length that's part of what ensures uniqueness?
>Maybe I should read that UUI and GUID ref in the footnote.
===========================================================================
To unsubscribe, send email to [EMAIL PROTECTED] and include in the body
of the message "signoff EJB-INTEREST". For general help, send email to
[EMAIL PROTECTED] and include in the body of the message "help".
