Return-Path: Delivered-To: apmail-incubator-geronimo-dev-archive@incubator.apache.org Received: (qmail 85755 invoked by uid 500); 11 Aug 2003 21:11:45 -0000 Mailing-List: contact geronimo-dev-help@incubator.apache.org; run by ezmlm Precedence: bulk list-help: list-unsubscribe: list-post: Reply-To: geronimo-dev@incubator.apache.org Delivered-To: mailing list geronimo-dev@incubator.apache.org Received: (qmail 85742 invoked from network); 11 Aug 2003 21:11:45 -0000 Received: from dns2.digitalglobe.com (205.166.175.35) by daedalus.apache.org with SMTP; 11 Aug 2003 21:11:45 -0000 Received: from comail.digitalglobe.com (comail.digitalglobe.com [10.10.42.3]) by dns2.digitalglobe.com (8.12.6/8.12.5) with ESMTP id h7BLBoxv059274 for ; Mon, 11 Aug 2003 15:11:51 -0600 (MDT) (envelope-from ferret@frii.com) Received: from pclnxbsnyder.digitalglobe.com ([10.10.30.169]) by comail.digitalglobe.com with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2656.59) id QXAGKVDG; Mon, 11 Aug 2003 15:11:50 -0600 Date: Mon, 11 Aug 2003 21:11:50 +0000 (GMT) From: Bruce Snyder X-X-Sender: bsnyder@pclnxbsnyder.digitalglobe.com To: geronimo-dev@incubator.apache.org Subject: Re: Caching In-Reply-To: <3F37E83C.4070401@apache.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N This one time, at band camp, Berin Loritsch said: BL>Alex Blewitt wrote: BL> BL>> It came to my attention in the org.apache.geronimo.cache package that a BL>> number of these things have been implemented already by the BL>> org.apache.excalibur.cache package. Perhaps someone with CVS access BL>> could put a comment in to potentially refactor these two together at a BL>> later stage? BL> BL>It would probably be worth it. Also the Excalibur "Store" includes another BL>cache implementation.... BL> BL>To further cloud the picture, I believe that there might be a Jakarta BL>Commons Cache implementation. BL> BL>A best of breed would be a good thing. Probably should evaluate it based BL>on the good points of each implementation and start with whatever is closest BL>to where we want to end up. This could be refactored to make use of the JCache API when it is finally released. This would make this layer pluggable. For now, we can make use of the java.util.Map interface right now as that is very close the yet to be seen JCache API. Bruce -- perl -e 'print unpack("u30","<0G)U8V4\@4VYY9&5R\"F9E