cocoon-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ard Schrijvers" <>
Subject RE: Custom Pipeline Caching - Using DelayedValidity?
Date Mon, 01 May 2006 09:56:48 GMT

"Well, after browsing around I wonder if I could use a delayed validity to implement this.
It would not help me skipping the request step for the external content, but I could get a
validity on the content and therefore skip the following transformers"

Yes, as I wrote on your other thread, if you can find the validity on the content, then you
could make it cacheable apart from having todo the request for the validity.

"Am I right with the delayed validity beeing the solution here?"

I am not sure why to use a delayed validity...all your generator should do, is that during
cocoon cachekey checking and validity checking, your generator should fetch something like
a timestamp of lastmodified of your external source. Has nothing to do with delayed validity
if you ask me. 

"What is the best start point to implement delayed validity (sample component)?"

If you are sure you need this one, look at the DirectoryGenerator and the TraxTransformer.
They both implement delayed validity (more precize, delayed agregated validity)

Check the end of, it really
might help you understanding cocoon cache,

Regards, AS

Oosteinde 11
1017WT Amsterdam
The Netherlands
Tel  +31 (0)20 5224466
------------------------------------------------------------- /



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

View raw message