Mailing-List: contact cocoon-dev-help@xml.apache.org; run by ezmlm
Precedence: bulk
Reply-To: cocoon-dev@xml.apache.org
To: cocoon-dev@xml.apache.org
Subject: Re: strange resons not going beta (was Re: C2: trouble getting
  streaming  to work as expected)
Message-ID: <985949698.3ac46602bb76d@mail.otego.com>
Date: Fri, 30 Mar 2001 12:54:58 +0200 (CEST)
From: Giacomo Pati <giacomo@apache.org>
References: <19C34CD863B1D4118E2800508BAF663A11C1F1@STONE>
 <3AC33BEF.5035E8AD@apache.org> <985875694.3ac344ef01eb2@mail.otego.com>
 <3AC35A0B.3A057996@apache.org> <3AC3B063.3090406@hisitech.com>
 <3AC4182A.952D9E36@apache.org> <3AC46279.4010505@hisitech.com>
In-Reply-To: <3AC46279.4010505@hisitech.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 8bit
User-Agent: IMP/PHP IMAP webmail program 2.2.4

Quoting Santiago Gala <sgala@hisitech.com>:

> 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.

Giacomo

> 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: cocoon-dev-unsubscribe@xml.apache.org
For additional commands, email: cocoon-dev-help@xml.apache.org