This one time, at band camp, Stephen Ince said:
SI>I thought I posted a fix to the castor news group but I have yet to see it.
SI>What is the protocol or the forum to post fixes?
SI>I noticed that in org.exolab.castor.persist.TransactionContext it was
SI>storing objects in a Vector and then subsequently removing and retreiving
SI>the object through an iterator. This is extremely inefficient. I added a
SI>SequencedHashtable and this sped up performance quite a bit. I wonder how
SI>pervasive this is in the Castor code.
You bring up a very valid point here. I am certainly in favor of
improving the performance of this type of lookup because it happens in a
number of areas throughout Castor. I want to continue this discussion,
but I'd rather have the discussion remain in a single thread on the
list. Let'stick to your first thread titled, 'performance patch for
TransactionContext.'
Bruce
--
perl -e 'print unpack("u30","<0G)[EMAIL PROTECTED]&5R\"F9E<G)E=\$\!F<FEI+F-O;0\`\`");'
The Castor Project
http://www.castor.org/
Apache Geronimo
http://incubator.apache.org/projects/geronimo.html
-----------------------------------------------------------
If you wish to unsubscribe from this mailing, send mail to
[EMAIL PROTECTED] with a subject of:
unsubscribe castor-dev
