On Wednesday 23 February 2005 23:40, Michael Giagnocavo wrote: > -----Original Message----- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] On Behalf Of > Tilghman Lesher > > >> >Currently, we have a 2 integer method, which is guaranteed to > >> > be machine-unique: unixtime and instance increment, which, as > >> > long as the daemon isn't constantly restarting, is fine. To > >> > add network uniqueness, the addition of a third integer should > >> > be sufficient: the 32-bit integer representation of the IP > >> > address. Oddly, that's 96 bits, 32 less than MD5, yet it's > >> > guaranteed to be unique for at least the next 30 years. > >> > >> What's wrong with using a GUID? > > > >Formulated how? I just explained how you could formulate one, > > which should be sufficient for an enterprising soul to code (even > > if that enterprising soul is me). > > Why not use uuid_generate?
Because uuid_generate suffers from the same problems as MD5: that is, because it is not based upon an algorithm which guarantees uniqueness, while it is random, there is the same probability of collisions as with MD5 (a probability which increases over time). -- Tilghman _______________________________________________ Asterisk-Dev mailing list [email protected] http://lists.digium.com/mailman/listinfo/asterisk-dev To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-dev
