You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commons-dev@ws.apache.org by Rodrigo Ruiz <rr...@gridsystems.com> on 2007/05/05 12:48:27 UTC

[AXIOM] About UUIDGenerator

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: commons-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: commons-dev-help@ws.apache.org

Re: [AXIOM] About UUIDGenerator

Posted by Rodrigo Ruiz <rr...@gridsystems.com>.
-----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: commons-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: commons-dev-help@ws.apache.org

Re: [AXIOM] About UUIDGenerator

Posted by Eran Chinthaka <ch...@opensource.lk>.
-----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: commons-dev-unsubscribe@ws.apache.org
> For additional commands, e-mail: commons-dev-help@ws.apache.org
> 
> 

-----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: commons-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: commons-dev-help@ws.apache.org