Return-Path: <balld@webslingerZ.com>
Mailing-List: contact cocoon-dev-help@xml.apache.org; run by ezmlm
Delivered-To: mailing list cocoon-dev@xml.apache.org
Received: (qmail 45978 invoked from network); 22 Jan 2001 23:38:43 -0000
Received: from rdu25-5-046.nc.rr.com (HELO akira.webslingerZ.com) (24.25.5.46)
  by h31.sny.collab.net with SMTP; 22 Jan 2001 23:38:43 -0000
Received: by akira.webslingerZ.com (Postfix, from userid 501)
	id CB7E8130A3; Mon, 22 Jan 2001 18:39:54 -0500 (EST)
Received: from localhost (localhost [127.0.0.1])
	by akira.webslingerZ.com (Postfix) with ESMTP id B24F960B2
	for <cocoon-dev@xml.apache.org>; Mon, 22 Jan 2001 18:39:54 -0500 (EST)
Date: Mon, 22 Jan 2001 18:39:54 -0500 (EST)
From: Donald Ball <balld@webslingerZ.com>
X-Sender: <balld@localhost.localdomain>
To: <cocoon-dev@xml.apache.org>
Subject: Re: idle thoughts in caching in c2
In-Reply-To: <3A6CAC6C.ACCDC07@apache.org>
Message-ID: <Pine.LNX.4.30.0101221839440.1571-100000@localhost.localdomain>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-Spam-Rating: h31.sny.collab.net 1.6.2 0/1000/N

On Mon, 22 Jan 2001, Giacomo Pati wrote:

> > * Sergio Carvalho (scarvalho@criticalsoftware.com) wrote :
> > > On Fri, 19 Jan 2001 13:44:42 -0500 (EST)
> > > Donald Ball <balld@webslingerZ.com> wrote:
> > > > do you mean that the caching components should be explicitly put in the
> > > > pipeline in the sitemap:
> > > >
> > > > <map:cache type="lru"/>
> > > 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.

that's my worry, honestly.

- donald