On 11.04.2007 07:51, Ard Schrijvers wrote:
@Joerg: you are confused with the pipeline in which not all components are cacheable components. In that case, Cocoon caches untill the first not cacheable component. So, in the original setup of one pipeline, if Fergus would replace the xsl transformer with a custom one, that would not implement CacheableProcessingComponent, then the total result of the pipeline would never be cached, but untill the transformer. Then, the transformer would always have to be done, and the generator ones (as long as the validities are valid). A call with a different sort order would thus be much faster in the single pipeline setup if the transformer was uncacheable....what a paradox :-)
Thanks, Ard. Your inside views are always appreciated and help to understand Cocoon internals a lot :)
Joerg --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
