<jo*****@driver.net> wrote in message news:eM**************@TK2MSFTNGP11.phx.gbl...
I was wondering if there would be any significant performance increases by
loading Xslt Files into the Application Variables if there were a single or
maybe multiple XSLT file(s) that would be used throughout a website. I do
not know if relieving the I/O burden would overcome the memory/hashtable
lookup from storing one or multiple XSLT Files in the Application Object.
Maybe the "Cache" object would be a better choice: you
could set a CacheDependency, so the cached item is removed when
the real file is changed (nice feature when developing).
But: there is one problem, specifically with xslt's! when you use
<xsl:include> elements, the processor knows where to look in
the case of a file, but needs some help when the xslt comes from a string.
(you need to supply an XmlResolver)
Hans Kesting