Return-Path: Mailing-List: contact cocoon-dev-help@xml.apache.org; run by ezmlm Delivered-To: mailing list cocoon-dev@xml.apache.org Received: (qmail 84596 invoked from network); 22 Jan 2001 10:35:36 -0000 Received: from serv01.fe.up.pt (HELO tweety.fe.up.pt) (193.136.33.231) by h31.sny.collab.net with SMTP; 22 Jan 2001 10:35:36 -0000 Received: from lorosae.fe.up.pt (root@lorosae.fe.up.pt [193.136.28.35]) by tweety.fe.up.pt (8.9.3/8.9.3) with ESMTP id KAA23031 for ; Mon, 22 Jan 2001 10:34:56 GMT Received: from rd-antares (scar@rd-antares.fe.up.pt [193.136.37.59]) by lorosae.fe.up.pt (8.10.1/8.10.1) with SMTP id f0MAYnR30871 for ; Mon, 22 Jan 2001 10:34:50 GMT Date: Mon, 22 Jan 2001 10:25:33 +0000 From: Sergio Carvalho To: cocoon-dev@xml.apache.org Subject: Re: idle thoughts in caching in c2 Message-Id: <20010122102533.7a023561.scarvalho@criticalsoftware.com> In-Reply-To: References: <20010119174249.3c9b6c7c.scarvalho@criticalsoftware.com> X-Mailer: Sylpheed version 0.4.9 (GTK+ 1.2.8; Linux 2.2.16; i686) Organization: Critical Software Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Spam-Rating: h31.sny.collab.net 1.6.2 0/1000/N On Fri, 19 Jan 2001 13:44:42 -0500 (EST) Donald Ball wrote: > On Fri, 19 Jan 2001, Sergio Carvalho wrote: > > > In my opinion, caching components should be part of the pipeline, > > allowing for different caching methods to be used, and combined with > > the different processors. In this scenario, cache doesn't even need to > > be snapshot-based. > > do you mean that the caching components should be explicitly put in the > pipeline in the sitemap: > > Yes. A Cache interface could be defined, so that classes implementing caching are identified. Then, these are placed in the pipeline, between each data-producer (or processor) and the subsequent data-consumer. Note that this doesn't invalidate a processor that handles its own caching (current C1 processors do this). They should be able to do just that, in cases where cache methods are heavily intertwined with the processing algorithm. But for all others (previously I used the xinclude processor as an example), cache handling is better off in a separate entity. > > or something else? > > - donald > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org > For additional commands, email: cocoon-dev-help@xml.apache.org > -- -- Sergio Carvalho --------------- scarvalho@criticalsoftware.com If at first you don't succeed, skydiving is not for you