cocoon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From brian moseley>
Subject Re: servlet or no? (was Re: [Moving on] SAX vs. DOM part II)
Date Tue, 25 Jan 2000 02:42:46 GMT
On Mon, 24 Jan 2000, Pierpaolo Fumagalli wrote:

> Ok... On this we agree (I believe). This is the cache mechanism how it
> should be deployed:
> The cocoon execution involves these steps:
>    a) producer
>    b) filter (one or more)
>    c) serializer
>    All together can build up a "cocoon chain"
> When I receive a request, I call everyone of those (a,b*,c) and ask
> "were you, your configurations, or those files your rely on modified
> since the last time I called you (and to be precise this -the previous
> request date-)?"
> If that says it changed, then I re-process the request, if not, I simply
> get the copy out of the cache and send it, or if the client (in HTTP)
> provided a "If-Modified-Since" header, and that's within our range, I
> don't serve anything.
> Is this right? Because if so, it's already carved in Cocoon 2.

yes, sounds good.

View raw message