On 04.08.2006 09:39, [EMAIL PROTECTED] wrote:
So the problem here is, that all parameters in the request are used for
caching. However, only those parameters used in the XSL stylesheet could
possibly change the outcome of the transformation. As far as I know,
these are exactly the parameters, which are declared as global
parameters in the stylesheet.
Even though I don't know which components play together when building
and accessing caches, that should be limited to parameters really used
in the stylesheet. I mean, the components responsible for caching have
to check for changes of the stylesheet anyway. (Probably just by
timestamp?) So anytime the stylesheet changed, they could have a look at
it, and find out which parameters are actually relevant for caching.
This might slow down the first use of a stylesheet quite a lot, but it
should fix the above caching issues.
That would be absolutely hard-core. You would need to re-implement half
an XSLT processor since there can be imports and includes. The interface
to the XSLT processor is used for setting the parameters. That's the
interface Cocoon is aware of and can grab the parameters easily used for
caching.
Joerg
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
