Return-Path: Delivered-To: apmail-db-ojb-dev-archive@www.apache.org Received: (qmail 22459 invoked from network); 27 Jun 2005 09:00:41 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur.apache.org with SMTP; 27 Jun 2005 09:00:41 -0000 Received: (qmail 32841 invoked by uid 500); 27 Jun 2005 09:00:40 -0000 Delivered-To: apmail-db-ojb-dev-archive@db.apache.org Received: (qmail 32806 invoked by uid 500); 27 Jun 2005 09:00:39 -0000 Mailing-List: contact ojb-dev-help@db.apache.org; run by ezmlm Precedence: bulk List-Unsubscribe: List-Help: List-Post: List-Id: "OJB Developers List" Reply-To: "OJB Developers List" Delivered-To: mailing list ojb-dev@db.apache.org Received: (qmail 32793 invoked by uid 99); 27 Jun 2005 09:00:39 -0000 Received: from asf.osuosl.org (HELO asf.osuosl.org) (140.211.166.49) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 27 Jun 2005 02:00:39 -0700 X-ASF-Spam-Status: No, hits=0.0 required=10.0 tests=RCVD_BY_IP X-Spam-Check-By: apache.org Received-SPF: pass (asf.osuosl.org: domain of tomdzk@gmail.com designates 64.233.182.205 as permitted sender) Received: from [64.233.182.205] (HELO nproxy.gmail.com) (64.233.182.205) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 27 Jun 2005 02:00:39 -0700 Received: by nproxy.gmail.com with SMTP id d4so162232nfe for ; Mon, 27 Jun 2005 02:00:35 -0700 (PDT) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:reply-to:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=Anxj8Fa7tT//JGJS8iV/3s85wiyWYTclRQfpv5fyWkjKtP/NOxMUs5QluYRXTYfJUwbsaePzorS+lbmL+3Cd99tGeXlAQuTaHYtn27KHoqnVgcsZG4I5jWzXyhISbcdbu3XqWICUdleiVNa7daiiw22GAp/ePcy7UcCQx7+YWvg= Received: by 10.48.249.6 with SMTP id w6mr105217nfh; Mon, 27 Jun 2005 02:00:35 -0700 (PDT) Received: by 10.48.249.2 with HTTP; Mon, 27 Jun 2005 02:00:35 -0700 (PDT) Message-ID: <224f323405062702007cac6f41@mail.gmail.com> Date: Mon, 27 Jun 2005 11:00:35 +0200 From: Thomas Dudziak Reply-To: Thomas Dudziak To: OJB Developers List Subject: Re: RFC: Multi-Level Timeouts for Default Cache In-Reply-To: <42BFB95D.7000902@apache.org> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline References: <316E5B943771D311BAC500805FD7A078043C1DA8@MAIL.osn.state.oh.us> <42BFB95D.7000902@apache.org> X-Virus-Checked: Checked by ClamAV on apache.org X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N > For me the logical place to put the time-to-live is at the ClassDescripto= r > level, since I think this info statically belongs to the class definition= . >=20 > I do not see the use-case where cache TTL for a specific class should be > different between different jcd:s? Imagine a larger-scale web application (load-balanced etc,) that is meant to run on a DB2 database. For development and unit test purposes the developers might probably want to use not a fully-fledged DB2 but rather a local (embedded) Derby. But with the cache-settings for the big database (which might even use a different cache altogether) this will likely lead to problems. =20 > I think it's enough with the current global cache-config TTL plus the > possibility to override it on the class-descriptor level. I was wondering whether a more configurable strategy will help here. For instance, we could allow the user to define the classification himself, e.g.

which can them be mapped in the cache-descriptor to timeouts (and other info where necessary):

This would allow for pluggable caches (e.g. a cache for a local database might define the same timeouts for these thus making them equivalent), and the developers can specify their intention regarding the longevity of the classes. Tom --------------------------------------------------------------------- To unsubscribe, e-mail: ojb-dev-unsubscribe@db.apache.org For additional commands, e-mail: ojb-dev-help@db.apache.org