Return-Path: Delivered-To: apmail-jakarta-commons-dev-archive@apache.org Received: (qmail 93808 invoked from network); 24 Jan 2002 21:41:48 -0000 Received: from unknown (HELO nagoya.betaversion.org) (192.18.49.131) by daedalus.apache.org with SMTP; 24 Jan 2002 21:41:48 -0000 Received: (qmail 26902 invoked by uid 97); 24 Jan 2002 21:41:51 -0000 Delivered-To: qmlist-jakarta-archive-commons-dev@jakarta.apache.org Received: (qmail 26865 invoked by uid 97); 24 Jan 2002 21:41:50 -0000 Mailing-List: contact commons-dev-help@jakarta.apache.org; run by ezmlm Precedence: bulk List-Unsubscribe: List-Subscribe: List-Help: List-Post: List-Id: "Jakarta Commons Developers List" Reply-To: "Jakarta Commons Developers List" Delivered-To: mailing list commons-dev@jakarta.apache.org Received: (qmail 26854 invoked from network); 24 Jan 2002 21:41:50 -0000 Content-Class: urn:content-classes:message Subject: RE: Silly Question MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Date: Thu, 24 Jan 2002 13:36:41 -0800 X-MimeOLE: Produced By Microsoft Exchange V6.0.5762.3 Message-ID: <458473676F1AC74A84EAB2F22004DA6D1B1E91@mail.nextance.com> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: Silly Question Thread-Index: AcGlGBVbu7Vt+3x+RPapOiTRfGVxXwABxMaA From: "Scott Sanders" To: "Jakarta Commons Developers List" X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N So then sandbox/util/SequencedHashtable can be removed? > -----Original Message----- > From: John McNally [mailto:jmcnally@collab.net]=20 > Sent: Thursday, January 24, 2002 12:47 PM > To: Jakarta Commons Developers List > Subject: Re: Silly Question >=20 >=20 > SequencedHashMap is the consequence of moving=20 > sandbox/util/SequencedHashtable into collections. So there=20 > is no reason to add SequencedHashtable again (this time as=20 > is.) I think what ought to be done is to fix the javadoc in=20 > both classes. >=20 > Remove the "This class is thread-safe" declaration in=20 > SequencedHashMap. >=20 > Add some text to SequencedHashtable to the affect of what=20 > Michael states below and deprecate it. >=20 > john mcnally=20 >=20 > "Michael A. Smith" wrote: > >=20 > > On Thu, 24 Jan 2002, Scott Sanders wrote: > > > > Are you asking whether SequencedHashtable should be=20 > committed to=20 > > > > the collections component unaltered? > > > > > > Yes. > >=20 > > I'm not a committer, so weigh my thoughts how you wish: In my=20 > > opinion, no. While a synchronized version may be=20 > worthwhile, I think=20 > > it would be better implemented wrapping the impl in=20 > SequencedHashMap=20 > > using Collections.synchronizedMap. Having it inherit from=20 > Hashtable=20 > > rather than HashMap doesn't really add anything other than=20 > increased=20 > > headache in maintenance (any bug fixes would need to be applied to=20 > > both SequencedHashtable and SequencedHashMap) > >=20 > > > >Asking whether > > > > no-JDK 1.2 collection types can go into the collections =20 > > > >component? > > > > > > Yes. > >=20 > > Again, I'm not a committer, so weigh my thoughts how you wish: The=20 > > commons collections component is attempting to fill "holes left=20 > > unfilled by Sun's implementations"[1]. Non-JDK 1.2-based=20 > collections=20 > > could appropriately fit within that charter, thus should=20 > certainly be=20 > > allowed in the collections component. For example, a Heap=20 > > implementation that orders things based on a priority=20 > specified when=20 > > inserting the item into the heap (requires add(Object o,=20 > int priority)=20 > > which doesn't exist anywhere in the JDK 1.2 collections API). > >=20 > > regards, > > michael > >=20 > > [1] http://jakarta.apache.org/commons/collections.html > >=20 > > -- > > To unsubscribe, e-mail: =20 > unsubscribe@jakarta.apache.org> > > For=20 > additional commands,=20 > e-mail:=20 > > >=20 > -- > To unsubscribe, e-mail: =20 > unsubscribe@jakarta.apache.org> > For=20 > additional commands,=20 > e-mail: >=20 >=20 -- To unsubscribe, e-mail: For additional commands, e-mail: