We are evaluating porting an existing CMS and web publishing system over to
cocoon but we have some issues with caching. In our particular situation we
normally use two different cache management strategies:
1. For automated feeds (newswires etc.) we use a time based expiration
2. For Editor
Steven :
DBPrism CMS uses this approach using ESI invalidation protocol
(http://www.w3.org/TR/esi-invp) that is an standard.
You could get more information about Cocoon's External Cache
Invalidator Server at
http://www.dbprism.com.ar/dbprism/doc/xdocs/Server.html
A flow of how the inva
Hello Steven,
**
First let me say that I am not a developer of cocoon, but a developer
who uses cocoon, so it's possible that I have something wrong here. If
so, anyone please feel free to correct me.
This code works with the released version, cocoon2.0.2
Additionally, I am running all o
> On Tue, 2002-05-14 at 14:56, Steven Sedlmeyer wrote:
> > We are evaluating porting an existing CMS and web publishing system over
to
> > cocoon but we have some issues with caching. In our particular
situation we
> > normally use two different cache management strategies:
> >
> > 1. For automa
ct: Re: Caching for database driven sites
> On Tue, 2002-05-14 at 14:56, Steven Sedlmeyer wrote:
> > We are evaluating porting an existing CMS and web publishing system over
to
> > cocoon but we have some issues with caching. In our particular
situation we
> > normally use two d
your ESI
work in the above scenario?
Geoff Howard
-Original Message-
From: Marcelo F. Ochoa [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, May 14, 2002 10:43 AM
To: [EMAIL PROTECTED]
Subject: Re: Caching for database driven sites
Steven :
DBPrism CMS uses this approach using ESI invalidat
Geoff Howard wrote:
>Marcelo (and anyone else listening) -
>
>
>
>We'll need (and so would others I think) something that de-couples this.
>For example, the database knows that the article table has been updated for
>record 323456 from the PAGELAYOUT table, but it doesn't (and shouldn't have
>to
Marcelo F. Ochoa wrote:
> AFAIK Cocoon's caching algorithm uses the URL information for making
> the caching key (long value returned by generateKey() method), look at
> the sources for org.apache.cocoon.util.HashUtil and
> org.apache.cocoon.generation.FileGenerator as an example.
> Obviusl
