You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@cocoon.apache.org by Gianugo Rabellino <gi...@apache.org> on 2002/06/07 09:37:38 UTC
Exipires headers (was: Re: Cocoon article on JDJ)
Ivelin Ivanov wrote:
> It's sad to read though that:
> 2) Cocoon is not applicable for large scale applications.
> With the new contribution for Expires response header and caching
> improvements, 2) shouldn't be a big deal any more.
> BTW, is Expires checked in already?
Definitely yes, in HEAD only. I still have to understand some quirks in
(reverse) proxy implementations, but it already works like a charm with
clients (browsers). I hope to have it working RSN ar 100% with cachine
enabled reverse proxies, but it already gives a sensible performance
boost as of now.
The other good news is that the whole Cocoon environment will have the
Expires information, since it's in the objectModel. This might lead to a
change in the cache algorithms (I'm waiting for Carsten to finish up his
event/stream cache unification to have a look at it), taking into
account even this information.
Diana: an HOWTO is on the way, I promise :-)
Ciao,
--
Gianugo Rabellino
---------------------------------------------------------------------
Please check that your question has not already been answered in the
FAQ before posting. <http://xml.apache.org/cocoon/faqs.html>
To unsubscribe, e-mail: <co...@xml.apache.org>
For additional commands, e-mail: <co...@xml.apache.org>
RE: Exipires headers (was: Re: Cocoon article on JDJ)
Posted by Carsten Ziegeler <cz...@s-und-n.de>.
Gianugo Rabellino wrote:
>
> The other good news is that the whole Cocoon environment will have the
> Expires information, since it's in the objectModel. This might lead to a
> change in the cache algorithms (I'm waiting for Carsten to finish up his
> event/stream cache unification to have a look at it), taking into
> account even this information.
>
The unification is finished - for now... :)
No, seriously, it's finished and working, but what is needed now, is
feedback if all are satisfied with this approach - so there might be
some minor changes here and there.
The new component is called ProcessingPipeline.
I changed the implementation of the expires headers by moving it from
the code of the tree processor to the implementation of the
ProcessingPipeline - so you will find everything in the
AbstractProcessingPipeline now.
Carsten
Carsten Ziegeler Chief Architect Open Source Group, S&N AG
------------------------------------------------------------------
Cocoon Consulting, Training and Projects
------------------------------------------------------------------
mailto:cziegeler@s-und-n.de http://www.s-und-n.de
http://ziegeler.bei.t-online.de
---------------------------------------------------------------------
To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org
For additional commands, email: cocoon-dev-help@xml.apache.org