This is the mail archive of the
xsl-list@mulberrytech.com
mailing list .
RE: Data in Stylesheets [was: Comments affect Performance?]
- To: "'xsl-list at mulberrytech dot com'" <xsl-list at mulberrytech dot com>
- Subject: RE: Data in Stylesheets [was: Comments affect Performance?]
- From: Kay Michael <Michael dot Kay at icl dot com>
- Date: Wed, 27 Sep 2000 16:15:07 +0100
- Reply-To: xsl-list at mulberrytech dot com
> -----Original Message-----
> From: Warren Hedley [mailto:w.hedley@auckland.ac.nz]
> Sent: 27 September 2000 14:45
> To: xsl-list@mulberrytech.com
> Subject: Data in Stylesheets [was: Comments affect Performance?]
>
>
> Kay Michael wrote:
> >
> > When the stylesheet is accessed as a source document (using
> document(""))
> > the same rules for whitespace and comments apply as for any
> other source
> > document. In Saxon, this means the stylesheet is re-parsed
> and a separate
> > tree is built.
>
> That's interesting. Does that mean that storing information
> in the stylesheet
> document, a common suggestion for solving search and replace
> problems, is
> probably not very efficient, because the processor is
> actually re-loading the stylesheet?
>
It means, with Saxon, that it's no more efficient than storing the data in a
separate file. Unless of course there is some OS or web server or browser
caching that makes it more efficient to read the same file twice than to
read two separate files.
XSLT processors that are DOM-based, like MSXML3, probably use a different
strategy (I'm guessing here) in which the whitespace and comments are not
actually removed from the tree but simply masked from the XSLT processor.
With these processors, the overhead of building two separate trees is
presumably avoided.
Mike Kay
XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list