-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 I am sorry I can not understand why it is not compliant with the standard.
Anyway, our intention was to use this in two places, mainly. First, when we handled attachments. In that case, we only need a unique id, whatever it is. Second case is to use it as message id. I think we are using it without a problem in all the above cases very well. At the same time this UUID generator was a perf bottleneck some time back and we hacked it a bit. So what is missing here? Please explain and help us to improve it. Thanks, Eran Chinthaka Rodrigo Ruiz wrote: > Looking at the source code of UUIDGenerator class I see it does not > generate standard compliant IDs. This could result in an interoperability > issue with systems. > > Was this ad-hoc approach selected intentionally? > > Regards, > Rodrigo > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.3 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFGPp6IjON2uBzUhh8RAjxDAJwLMHgqaYbFX/720iZGwCXt6Pd/BwCglsvW qGusKW+8L6Mr7rcXbIHZxqw= =4YI8 -----END PGP SIGNATURE----- --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
