commons-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From bugzi...@apache.org
Subject DO NOT REPLY [Bug 23270] - New features required for DoubleOreredMap
Date Fri, 19 Sep 2003 15:58:11 GMT
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://nagoya.apache.org/bugzilla/show_bug.cgi?id=23270>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://nagoya.apache.org/bugzilla/show_bug.cgi?id=23270

New features required for DoubleOreredMap





------- Additional Comments From apacheBugzilla@AMammenT.cotse.net  2003-09-19 15:58 -------
Couple of questions/ideas....

First of all, it might make sense to separate into separate patches the work 
for using comparators for ordering, decorators, and the work for transaction 
support.  I think the use of comparators to determine the order in the tree is 
a great idea.  It's also a fairly small modification to the contract of 
DoubleOrderedMap while very much in line with the purpose of the map suggested 
by it's name.  Likewise for decorators....  

With respect to the transaction support (probably the most significant change 
to the current contract, and therefore the most likely to provoke discussion): 
Any thought of providing the transaction support either through a wrapper for 
Maps in general (but this does not solve your specific need for the 
DoubleOrderedMap which has an extended contract), or as a helper of some sort 
which can be used to quickly modify very many different 
Maps/Collections/Containers through delegation.  I don't know if its feasible, 
but if people do want the transaction support (and I do see a use for it), 
then it would be nice to have a way to provide that support for many classes 
across spectrum of available classes.  

Just throwing out some ideas.

Mime
View raw message