forrest-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From David Crossley <>
Subject Re: Include mechanism for forrest...
Date Mon, 17 Oct 2005 08:47:12 GMT
Ross Gardler wrote:
> David Crossley wrote:
> >Also Cocoon will cache the results of each pipeline, so if
> >the xincluded file changes, then the changes will have
> >no effect.
> The XInclude transformer is not cacheable. This is good with respect to 
> the problem you identify, but bad with respect to performance issues, 
> since the include is processed regardless of whether the included 
> document is changed, thus the generated document can never be cached.

Ah yeah, sorry. I had things the wrong way around.

So it is not a practice that we want to encourage,
though if people want to do it, then they should be
able to. Akin to using the document() function.


> For simple includes we should use CInclude instead, this is cacheable, 
> however, CInclude does not allow the use of XPath so does not fit this 
> use case.
> Ross

View raw message