[ http://issues.apache.org/jira/browse/AXIS2-282?page=comments#action_12332226 ]
Eran Chinthaka commented on AXIS2-282: -------------------------------------- Rajesh, Ant also initialy came up with this suggestion and our Sandesha people also wanted to include the commons UUID generator initialy. I answered to this question to Ant in the Synapse dev list, but let me put that here also for tracking purposes. "Well, you all agree that we need a UUID generator. This is required for creating message ids, MTOM ids, Sandesha stuff, etc.. We could have easily taken the commons UUID generator, but that will add another jar to Axis2. When that happens you people will shout and say, Axis2 download is large. So I try my level best to avoid adding new jars. Thilina and Dims were kind enough to write an acceptable level of UUID generator for Axis2 which we are using. " For this I got an excellent suggestion from Ant and created this issue from that and then I implemented that in Axis2. I personally like to avoid new jars as much as possible. But if you have a better algorithm, lets implement that in Axis2. I think the current algorithm will give us a uniqueness which we all can satisfy at least for the time being. If our one is not smart enough to handle future stuff, then lets think about shifting a specialised UUID generator later. > Axis2 UUID Generator is too slow > -------------------------------- > > Key: AXIS2-282 > URL: http://issues.apache.org/jira/browse/AXIS2-282 > Project: Apache Axis 2.0 (Axis2) > Type: Improvement > Components: core > Reporter: Eran Chinthaka > Fix For: 0.93 > > According to Ant Elder : Calling to UUIDGenerator.getUUID() is _really_ slow, > takes about > 1ms on my machine, accounting for about 65% of the total service invocation! > Solution Proposed by him : To make the UUID generator a bit faster how about > doing all the complicated > computation to come up with a unique ID just the one time, then for all > subsequent requests just append an incrementing integer onto the original > unique id. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
