|
The specific thing
you describe you want to implement is not possible. But, there are options to
improve on some points, but it really depends on a few things (especially
getting the external content):
I will try to
summarize some of your options here:
1) How up to date
should the external content be? Can you say, it is valid for at least 5 minutes?
Then, use the expiring cche of cocoon
2) Can you get a
timestamp of the external content (just like on filesystem, a lastmodified)?
Then, normal cocoon cache should work. Only disadvantage, is that for checking
the validity of your cached pipeline, a call to the external resource is made
for something like a timestamp.
3) This is by far
the nicest solution, but probably not useable for you: if you have external
calls to for example a repository, eventCaching is the way to go, where for
example after changes, jms messages invalidate the corresponding pipelines. But,
probably, you just read external content which is not yours.
These are your
options I think.
If you want to
understand more about the cocoon caching mechanism, and how cocoon checks for
cached pipelines (especially what the order of checks are, like cache keys and
validity objects), check out:
Regards Ard
--
Hippo Oosteinde 11 1017WT Amsterdam The Netherlands Tel +31 (0)20 5224466 ------------------------------------------------------------- [EMAIL PROTECTED] / http://www.hippo.nl -------------------------------------------------------------- Hello
Antonio,
I am not sure whether I can use the ExpiresCachingPipeline because I am implementing a kind of Proxy, so I have to make sure the content is up2date. To explain it better, here a simple description of the pipeline: 1. Transformations (Preparation) 2. Fetching of external content 3. Transformation After having fetched the content, I can decide if it changed or not, so I could skip step 3. I can't cache step 2 as I can never be sure that the external content did not change... How can I implement a cache mechanism for my special case? Hi Nils, |
- RE: Custom Pipeline Caching Ard Schrijvers
- Re: Custom Pipeline Caching Nils Kaiser
- RE: Custom Pipeline Caching Ard Schrijvers
