cocoon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From macie...@tiger.com.pl
Subject Re: AW: ContentAggregation and caching
Date Fri, 06 Jul 2001 15:01:36 GMT
On 5 Jul 2001, at 16:14, Carsten Ziegeler wrote:

> > Vadim Gritsenko wrote:
> > 
> > Carsten,
> > 
> > After you added "cocoon:" protocol, caching does not work anymore for
> > aggregated pipelines. Do you have any plans on reviving this feature?
> > 
> Yes, of course - but unfortunately time is currently very limited.
> So if someone else wants to go with this...
> 
> Here is my suggestion for a working solution:
> 
> >>
> For making this work the only change should be to the CocoonSourceFactory.
> This must only calculate a valid last modification date for the 
> whole pipeline. 
> As this is a EventPipeline the last modification date can only be
> available/valid if the whole pipeline is cacheable. 
> The last modification could then be fetched from the time the
> response of this eventpipeline was put into the cache.
> <<
> 

Does it mean than CachedEventObject should be extended to contain  
time  the eventpipeline has  been put into the cache?


Maciek Kaminski
maciejka@tiger.com.pl

---------------------------------------------------------------------
To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org
For additional commands, email: cocoon-dev-help@xml.apache.org


Mime
View raw message