It caches the loaded xslt file with a CacheDependency on the file. However it doesn't cache the generate html and the xslt transformation is applied on every page access.
Do you think caching the generated html would be of benefit? What about an optional parameter in a config file (or on the control) that could set caching on or off?
I sometimes import one xslt file into another and having this default xslt file caching can be a pain. If you edit the 'child' xslt file then the cache isn't refershed, you also need to edit the main xslt to get the cache to refresh.
I'll add caching option support for the next release. Do you think cacheXslt="true/false" and cacheHtml="true/false" at both a Control and global level would be enough?
The "cacheXslt" / "cacheHtml" attributes would be the way to go... with the "cacheXslt" to true, and cacheHtml to false as default.
With adding these extra capibilities to the XslResult control it is not becoming more like creating a macro (without actually creating the macro)? But isn't that the whole point?
If so, then might be worthwhile suggesting it for inclusion in the Umbraco core? (I think it's too late for v4.1, but v5 maybe?)
I've released a new version with additional optional caching parameters. The idea behind this control is to use xslt's without creating any macros (and to reduce the required number of DB calls on the front end)
I'd be more than happy for this to go back into the core.
Caching
Looks cool. I'm looking forward to trying it out. Does it support caching?
/Jesper
Hi Jesper,
It caches the loaded xslt file with a CacheDependency on the file. However it doesn't cache the generate html and the xslt transformation is applied on every page access.
Do you think caching the generated html would be of benefit? What about an optional parameter in a config file (or on the control) that could set caching on or off?
I sometimes import one xslt file into another and having this default xslt file caching can be a pain. If you edit the 'child' xslt file then the cache isn't refershed, you also need to edit the main xslt to get the cache to refresh.
I'll add caching option support for the next release. Do you think cacheXslt="true/false" and cacheHtml="true/false" at both a Control and global level would be enough?
Chris
The "cacheXslt" / "cacheHtml" attributes would be the way to go... with the "cacheXslt" to true, and cacheHtml to false as default.
With adding these extra capibilities to the XslResult control it is not becoming more like creating a macro (without actually creating the macro)? But isn't that the whole point?
If so, then might be worthwhile suggesting it for inclusion in the Umbraco core? (I think it's too late for v4.1, but v5 maybe?)
Done!
I've released a new version with additional optional caching parameters. The idea behind this control is to use xslt's without creating any macros (and to reduce the required number of DB calls on the front end)
I'd be more than happy for this to go back into the core.
Enjoy,
Chris
I really wish there was an 'Updated Projects' list on the projects page.... it'd give updates like this more visibility.
How does the caching of xslt transformation output work:
Is the output cached with a depency on the file or cached xslt?
For how long does it keep the cache?
Does it cache the output once for the template or page or user or both user and page?
As you might understand I wish for even more configurable caching options!
Hi Chris!
So to disable caching completely one just have to set cacheXslt="false" and cacheHtml="false", right?
If one would like to have cache per user, one need a regular macro, right? ("cache personalized")
Regards
Jonas
Yep that's correct.
There's no way to configure XLSTResult for personal caching.
is working on a reply...