Mailing-List: contact cocoon-dev-help@xml.apache.org; run by ezmlm
Precedence: bulk
Reply-To: cocoon-dev@xml.apache.org
From: "Vadim Gritsenko" <vadim.gritsenko@verizon.net>
To: <cocoon-dev@xml.apache.org>,
	<Michael.Melhem@managesoft.com>
Subject: RE: [PROPOSAL] Simple proposal to add "flushing" to Store components
Date: Mon, 12 Aug 2002 09:24:59 -0400
Message-ID: <00fd01c24203$a86a0250$0a00a8c0@vgritsenkopc>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit
In-Reply-To: 
 <Pine.LNX.4.43.0208121345580.312-100000@fztig938.bank.dresdner.net>
Importance: Normal

> From: Michael Melhem [mailto:michaelm@fztig938.bank.dresdner.net]
> 
> Dear Cocooners,
> 
> I would to like add a manual flushing ability
> to Store/Cache objects. That is, a method to emtpy
> a store component of all the data its currently holding.
> 
> This would be useful during appliction testing, if one needed to
ensure
> the cache is empty before a particualr request etc .
> 
> Moreover an adminstration application might want to manually flush
> the cache of some cocoon application running in production land etc
etc
> 
> Does any anyone see any issues with this little enhancememt, comments
?

Flushing or clearing? In MRU memory store, flush might mean "flush to
persistent store". I would suggest to use name clear(), and it is
consistent with collections API.

There is one issue with your proposal though: first, you have to
convince Avalon guys: Store components were moved to the Excalibur.


Vadim

> Regards,
> Michael Melhem


---------------------------------------------------------------------
To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org
For additional commands, email: cocoon-dev-help@xml.apache.org