Return-Path: Delivered-To: apmail-jakarta-commons-dev-archive@apache.org Received: (qmail 25175 invoked from network); 20 Jun 2002 18:29:31 -0000 Received: from unknown (HELO nagoya.betaversion.org) (192.18.49.131) by daedalus.apache.org with SMTP; 20 Jun 2002 18:29:31 -0000 Received: (qmail 2208 invoked by uid 97); 20 Jun 2002 18:29:38 -0000 Delivered-To: qmlist-jakarta-archive-commons-dev@jakarta.apache.org Received: (qmail 2192 invoked by uid 97); 20 Jun 2002 18:29:37 -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 2180 invoked by uid 98); 20 Jun 2002 18:29:37 -0000 X-Antivirus: nagoya (v4198 created Apr 24 2002) Reply-To: From: "Berin Loritsch" To: "'Jakarta Commons Developers List'" Subject: RE: [Commons-Avalon:collections] code integration Date: Thu, 20 Jun 2002 14:29:03 -0400 Message-ID: <006201c21888$5aab2660$ac00a8c0@Gabriel> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook, Build 10.0.2627 In-Reply-To: X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000 Importance: Normal X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N > From: Michael A. Smith [mailto:mas@apache.org] > > I understand that Hashtable is synchronized. I didn't > understand how it > was relevant to the discussion at that point. I guess I don't get the picture of how it is used in the approach that you outlined. However, if we go the route of FixedSizeXXX and VariableSizeXXX then it really doesn't matter. We can compare the cases where they are similar, and the cases where they excell. -- To unsubscribe, e-mail: For additional commands, e-mail: