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 5604 invoked from network); 22 Jan 2001 23:58:19 -0000 Received: from mail1.svr.pol.co.uk (195.92.193.18) by h31.sny.collab.net with SMTP; 22 Jan 2001 23:58:19 -0000 Received: from modem-102.north-dakota.dialup.pol.co.uk ([62.137.85.102] helo=hydrogen) by mail1.svr.pol.co.uk with esmtp (Exim 3.13 #0) id 14Kqqt-0006Mv-00 for cocoon-dev@xml.apache.org; Mon, 22 Jan 2001 23:58:24 +0000 Received: from paulr by hydrogen with local (Exim 3.20 #1 (Debian)) id 14Kqqt-000293-00 for ; Mon, 22 Jan 2001 23:58:23 +0000 Date: Mon, 22 Jan 2001 23:58:23 +0000 From: Paul Russell To: cocoon-dev@xml.apache.org Subject: Re: idle thoughts in caching in c2 Message-ID: <20010122235823.C562@hydrogen.internal.luminas.co.uk> Reply-To: Paul Russell References: <20010119174249.3c9b6c7c.scarvalho@criticalsoftware.com> <20010122102533.7a023561.scarvalho@criticalsoftware.com> <20010122110941.E601@hydrogen.internal.luminas.co.uk> <3A6CAC6C.ACCDC07@apache.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.3.12i In-Reply-To: <3A6CAC6C.ACCDC07@apache.org>; from giacomo@apache.org on Mon, Jan 22, 2001 at 10:55:56PM +0100 Sender: Paul Russell X-Spam-Rating: h31.sny.collab.net 1.6.2 0/1000/N * Giacomo Pati (giacomo@apache.org) wrote : > Paul Russell wrote: > > * Sergio Carvalho (scarvalho@criticalsoftware.com) wrote : > > > On Fri, 19 Jan 2001 13:44:42 -0500 (EST) > > > Donald Ball wrote: > > > > 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. > > That makes sense. > Are you sure? Is a sitemap maintainer skilled to specify where to cache > intermediate pipeline results? I doubt. If a sitemap manager isn't, who is? The sitemap managers' job is very definately a skilled position. I am more than happy that the sitemap should decide on caching policies when we can either: * get to the point that either we can write sensible heuristics for this; * write sensible learning algorithms to let the system decide on the parameters for caching. However, I think we should give sitemap managers the option to override these decisions, in case we (or the programs we write) get it wrong. I'd be interested in how other people visualise this? Should we make it *totally* explicit (I'm -0 on this -- I'd rather we let the engine 'play'), should we make it totally implicit (and risk sub-optimal performance)? Anything else? P. -- Paul Russell Email: paul@luminas.co.uk Technical Director Tel: +44 (0)20 8553 6622 Luminas Internet Applications Fax: +44 (0)870 28 47489 This is not an official statement or order. Web: www.luminas.co.uk