|P is for Practical|
Re^2: Generate a unique IDby BrowserUk (Pope)
|on Nov 15, 2010 at 13:20 UTC||Need Help??|
The basic one is that with any mechanism that has random numbers at its core, there is no guarantee of uniqueness, despite what Data::UUID POD says. (If you look up the RFC it uses the phrase: "is either guaranteed to be different from all other UUIDs/GUIDs generated until 3400 A.D. or extremely likely to be different".
The probability of collision might be very small, but it still exists. It would therefore be necessary to record enough information to disambiguate between chance collisions. And that means recording all the information that went into generating the number in the first place. As I wouldn't have access to all the information, that isn't possible.
A second reason is that the timestamping mechanisms used by Data::UUID are broken.
While the spec calls for a once-only randomly initialised, thereafter monotically increasing, sequence component, I can see no provision for storing/retrieving this on windows systems.
The output of the true_random() function is suspect on systems where rand()is limited to 15 bits.
As my needs are limited to a single system, using a deterministic value with a self-consistent, high resolution time component will suffice.
Examine what is said, not who speaks -- Silence betokens consent -- Love the truth but pardon error.
"Science is about questioning the status quo. Questioning authority".
In the absence of evidence, opinion is indistinguishable from prejudice.