cocoon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Giacomo Pati <>
Subject Re: Caching system idea (was: status on c2?)
Date Wed, 17 Jan 2001 16:12:14 GMT
Sergio Carvalho wrote:
> Why isn't caching implemented as just one another element in the pipeline?
> Much like HTTP proxies get in the request path implmenting caching.

You better use a proxy for this between your C2 and the clients (BTW I've 
tested this and it really rocks that way).

Caching is much mor that "another element in the pipeline". It might be one 
component between every pipeline "element" to get at all cachable stages in 
the production of a resource. Interfaces on the components should state if 
the output of that component is cachable and an algorithm which determines 
the point in a pipeline where caching should start or cached data should 
replayed into the pipeline must be found.


> It would allow different caching systems to be used throughout the page
> generation process, and would allow developers to see clearly where is
> output caching is being used.
> If I'm babbling, please ignore me :-) I'm using Cocoon 1 heavily, but
> although I've read the sparse docs on C2, I've had no time yet to test
> drive C2 and browse the code.
> --
> Sergio Carvalho
> ---------------
> If at first you don't succeed, skydiving is not for you
> On Wed, 17 Jan 2001 10:05:31 +0100
> Giacomo Pati <> wrote:
> > Try it NOW :) with the caching system. If you are a long time lurker on
> > this list you should have been aware of all the issues that are brought
> > up concerning caching.
> >
> > Send patches made to existing classes with "cvs diff -u" and the new
> > sources as tar/zip.
> >
> > TIA
> ---------------------------------------------------------------------
> To unsubscribe, e-mail:
> For additional commands, email:

View raw message