commons-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Scott Sanders" <ssand...@nextance.com>
Subject RE: Silly Question
Date Thu, 24 Jan 2002 21:36:41 GMT
So then sandbox/util/SequencedHashtable can be removed?

> -----Original Message-----
> From: John McNally [mailto:jmcnally@collab.net] 
> Sent: Thursday, January 24, 2002 12:47 PM
> To: Jakarta Commons Developers List
> Subject: Re: Silly Question
> 
> 
> SequencedHashMap is the consequence of moving 
> sandbox/util/SequencedHashtable into collections.  So there 
> is no reason to add SequencedHashtable again (this time as 
> is.)  I think what ought to be done is to fix the javadoc in 
> both classes.
> 
> Remove the "This class is thread-safe" declaration in 
> SequencedHashMap.
> 
> Add some text to SequencedHashtable to the affect of what 
> Michael states below and deprecate it.
> 
> john mcnally 
> 
> "Michael A. Smith" wrote:
> > 
> > On Thu, 24 Jan 2002, Scott Sanders wrote:
> > > > Are you asking whether SequencedHashtable should be 
> committed to 
> > > > the collections component unaltered?
> > >
> > > Yes.
> > 
> > I'm not a committer, so weigh my thoughts how you wish:  In my 
> > opinion, no.  While a synchronized version may be 
> worthwhile, I think 
> > it would be better implemented wrapping the impl in 
> SequencedHashMap 
> > using Collections.synchronizedMap.  Having it inherit from 
> Hashtable 
> > rather than HashMap doesn't really add anything other than 
> increased 
> > headache in maintenance (any bug fixes would need to be applied to 
> > both SequencedHashtable and SequencedHashMap)
> > 
> > > >Asking whether
> > > > no-JDK 1.2 collection types can go into the collections  
> > > >component?
> > >
> > > Yes.
> > 
> > Again, I'm not a committer, so weigh my thoughts how you wish:  The 
> > commons collections component is attempting to fill "holes left 
> > unfilled by Sun's implementations"[1].  Non-JDK 1.2-based 
> collections 
> > could appropriately fit within that charter, thus should 
> certainly be 
> > allowed in the collections component.  For example, a Heap 
> > implementation that orders things based on a priority 
> specified when 
> > inserting the item into the heap (requires add(Object o, 
> int priority) 
> > which doesn't exist anywhere in the JDK 1.2 collections API).
> > 
> > regards,
> > michael
> > 
> > [1] http://jakarta.apache.org/commons/collections.html
> > 
> > --
> > To unsubscribe, e-mail:   
> <mailto:commons-dev-> unsubscribe@jakarta.apache.org>
> > For 
> additional commands, 
> e-mail: 
> > <mailto:commons-dev-help@jakarta.apache.org>
> 
> --
> To unsubscribe, e-mail:   
> <mailto:commons-dev-> unsubscribe@jakarta.apache.org>
> For 
> additional commands, 
> e-mail: <mailto:commons-dev-help@jakarta.apache.org>
> 
> 

--
To unsubscribe, e-mail:   <mailto:commons-dev-unsubscribe@jakarta.apache.org>
For additional commands, e-mail: <mailto:commons-dev-help@jakarta.apache.org>


Mime
View raw message