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 18:32:21 GMT
The one in commons-util is the one I am referring to.  Hashtable also
differs from HashMap in that it is threadsafe (ie slower), if you need
that.

Scott

> -----Original Message-----
> From: Michael A. Smith [mailto:iammichael@iammichael.org] 
> Sent: Thursday, January 24, 2002 9:50 AM
> To: Jakarta Commons Developers List
> Subject: RE: Silly Question
> 
> 
> On Thu, 24 Jan 2002, Scott Sanders wrote:
> > But doesn't SequencedHashMap use the collections API?  What if, for 
> > some extremely crazy reason, you can't (JDK 1.0)?  Hashtable != 
> > HashMap, people.
> 
> The collections component specifies that its objects conform 
> to the Java2 collections API:
> 
> http://jakarta.apache.org/commons/collections.html
> 
> In any case, take a look at the SequencedHashtable 
> implementation in the utils sandbox.  While it extends 
> "Hashtable" rather than "HashMap", that doesn't make it JDK 
> <=1.1 compatible.  Just looking at the imports demonstrates 
> the SequencedHashtable is not <=1.1 compatible:
> 
>   import java.util.LinkedList;
>   import java.util.List;
>   import java.util.Map;
>   import java.util.Set;
> 
> regards,
> michael
> 
> 
>  >
> > Scott
> >
> > > -----Original Message-----
> > > From: Janek Bogucki [mailto:yan@studylink.com]
> > > Sent: Thursday, January 24, 2002 2:08 AM
> > > To: Jakarta Commons Developers List
> > > Subject: Re: Silly Question
> > >
> > >
> > > It's already in commons-collections 1.1-dev as 
> SequencedHashMap, and 
> > > very useful it is too :)
> > >
> > > -Janek
> > >
> > > > From: "Scott Sanders" <ssanders@nextance.com>
> > > > Reply-To: "Jakarta Commons Developers List" 
> > > > <commons-dev@jakarta.apache.org>
> > > > Date: Wed, 23 Jan 2002 21:00:56 -0800
> > > > To: <commons-dev@jakarta.apache.org>
> > > > Subject: Silly Question
> > > >
> > > > In the sanbox in utils, there exists a SequencedHashtable.
> > > >
> > > > Other than the obvious, why is this not in
> > > commons-collections? Are we
> > > > saying that something has to implement/extend the
> > > Collections API to
> > > > be included?
> > > >
> > > > The PROPOSAL.html states that collections was intended for
> > > ADTs, not
> > > > just Collections API stuff.
> > > >
> > > > So can we say that anything collectionesque (ie, hastables, 
> > > > vectors,
> > > > etc) should also be included?
> > > >
> > > > I think that commons-collections is small enough to warrant the 
> > > > inclusion of this SequencedHashtable, and possibly others,
> > > as I find
> > > > them.
> > > >
> > > > I will start adding these to commons-collections. Can I 
> get some 
> > > > feedback, maybe even some +1s?
> > > >
> > > > Scott Sanders
> > > >
> > > > --
> > > > 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>
> >
> 
> 
> 
> --
> 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