cocoon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Giacomo Pati <>
Subject Re: strange resons not going beta (was Re: C2: trouble getting streaming to work as expected)
Date Fri, 30 Mar 2001 10:54:58 GMT
Quoting Santiago Gala <>:

> Giacomo Pati wrote:
> > Santiago Gala wrote:
> > 
> >> I agree, except for some SVG examples, for instance the svg-welcome.
> A
> >> cache would be great to have some kinds of processing, like svg or
> pdf.
> >> 
> >> I would sell very well an automated generation of graphic navigation
> >> bars, for instance, but that calls for a cache, obviously.
> > 
> > 
> > For these types of caching you best put C2 behinde a proxy server.
> > 
> Or even configuring a "Expires:" Header, so that the client caches it. 
> But this would defeat part of the dynamic nature of some menus like
> these.
> BTW, is there any simple way that cocoon controls "If-modified-since:" 
> headers before the cache is in place? I imagine that part of the caching
> subsystem will/could take care of these shortcuts, not even delivering 
> content.

The readers (ResourceReader, DatabaseReader) we have are already handling 
"If-modified-since" requests and are able to accept a expires parameter to 
specify the TTL of a produced resource.


> Again, I'm not protesting (neither I have any authority for doing it :).
> Just pointing that cache is required for a "final" c2 that is usable. 
> That it happens under 2.0 or 2.1, or even that you release (as Donald 
> suggested) nightly c2aX builds, instead of fully freezing APIs, that's 
> your decision.
> On the other side, I agree that C2 needs more visibility, and it needs 
> it sooner than after. Freezing 2.0 APIs, and then, it caching needs API 
> changes, releasing it as 2.1 could be a solution.

To unsubscribe, e-mail:
For additional commands, email:

View raw message