Re: Custom Pipeline Caching - Using DelayedValidity?

[Nils Kaiser]

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. Am I right with the delayed validity beeing the solution here? What is the best start point to implement delayed validity (sample component)? Greetings, Nils Hello, I have a complex pipeline which contains some self written components that generate and transform data in steps that cannot really be cached (dependent on external resources like the result of a request...). What are the possibilities to implement a custom cachin scheme? Is there a way to define a step in the pipeline where caching is possible again (not just if all preceding components are cache-aware?). Greetings, Nils