|
Well I think in my environment step 2 is the way to
go... Creating a timestamp or cache-key might not be a problem. The
only thing might be that the content to fetch is itself initialized by
some transformations and therefore submitted as SAX events, which gives
me the problem that I would need to get access to the pipeline content
and beeing able to return my timestamp during transform... Is that possible? Sounds not really cocoon-like ;) I don't want to skip the fetching of the external content because up-to-date data is a strong requirement in my case. So what I need is a way to skip the following transforms. Thx, Nils Ard Schrijvers schrieb:
|
- Re: Custom Pipeline Caching Nils Kaiser
- RE: Custom Pipeline Caching Ard Schrijvers
