On 11/30/06, Jorge Godoy <[EMAIL PROTECTED]> wrote: > "Bob Ippolito" <[EMAIL PROTECTED]> writes: > > > There's always the chance of getting the same random number twice.. A > > timestamp with enough precision is generally better. It's *extremely* > > unlikely that a single user is going to get the same exact timestamp > > twice... there would have to be something seriously wrong with their > > UA for that to happen. > > What's the precision for the timestamp? If it doesn't get to at least > milliseconds then it starts being a problem with daylight saving time, > when the time change occurs.
Date.prototype.getTIme() is defined as an integer number of milliseconds since the epoch. Daylight savings time or any other timezone change is totally irrelevant, regardless of the precision. Even if it was relevant, the chances of doing a request precisely one hour after a previous request during the one hour per year in which that happens is a whole lot less than getting the same random number twice during any session at any time of the year. Especially considering the fact that most normal people are sleeping during (at least) the second 2am... -bob --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "MochiKit" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/mochikit?hl=en -~----------~----~----~----~------~----~------~--~---
