-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi Eran,
I was referring to the IETF standard (RFC 4122), sorry for the confusion :-) BTW, I was looking at the code because I was curious about the WSCOMMONS-201 bug, which I see your have already fixed :-) Cheers, Rodrigo Ruiz Eran Chinthaka wrote: > 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 > > - -- - ------------------------------------------------------------------- GRID SYSTEMS, S.A. Rodrigo Ruiz Parc Bit - Edificio 17 Research Coordinator 07121 Palma de Mallorca Baleares - Spain http://www.gridsystems.com/ - ------------------------------------------------------------------- -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.4 (MingW32) iD8DBQFGQZxHp9m/F5UenDoRAluUAKDMHRvnC5yj3RxTEk+NPCCHWrKDmQCfT6hS PEHEB4wZjbsY+37MjQiVfEA= =BWlE -----END PGP SIGNATURE----- --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
