Return-Path: Delivered-To: apmail-jakarta-commons-dev-archive@apache.org Received: (qmail 8965 invoked from network); 27 Nov 2002 09:49:40 -0000 Received: from unknown (HELO nagoya.betaversion.org) (192.18.49.131) by daedalus.apache.org with SMTP; 27 Nov 2002 09:49:40 -0000 Received: (qmail 25886 invoked by uid 97); 27 Nov 2002 09:50:51 -0000 Delivered-To: qmlist-jakarta-archive-commons-dev@jakarta.apache.org Received: (qmail 25870 invoked by uid 97); 27 Nov 2002 09:50:51 -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 25856 invoked by uid 50); 27 Nov 2002 09:50:50 -0000 Date: 27 Nov 2002 09:50:50 -0000 Message-ID: <20021127095050.25855.qmail@nagoya.betaversion.org> From: bugzilla@apache.org To: commons-dev@jakarta.apache.org Cc: Subject: DO NOT REPLY [Bug 14889] New: - ReferenceMap contract X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT . 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=14889 ReferenceMap contract Summary: ReferenceMap contract Product: Commons Version: 1.0 Beta 1 Platform: All OS/Version: All Status: NEW Severity: Normal Priority: Other Component: Collections AssignedTo: commons-dev@jakarta.apache.org ReportedBy: efrancos@incontext.fr I switched from SoftRefHashMap to ReferenceMap and I noticed that the purge method as become private and is called in many places in the source code, but the documentation for the method states that it is called only for write operations. I must be sure that the stale mappings are removed for read operations too (ex:size) and though currently the implementation calls purge() for all read methods as well this may change in the future. I think that calling purge on all [relevant] public methods is the right approach to preserve a coherent state. -- To unsubscribe, e-mail: For additional commands, e-mail: