This is the mail archive of the
xsl-list@mulberrytech.com
mailing list .
DOM input to Saxon (was: MSXML vs. Saxon: different handling of tabs & newlines)
- To: xsl-list at mulberrytech dot com
- Subject: DOM input to Saxon (was: MSXML vs. Saxon: different handling of tabs & newlines)
- From: "K. Ari Krupnikov" <ari at iln dot net>
- Date: Mon, 06 Nov 2000 12:42:17 -0800
- References: <FA209FE12D83D411BC970010A80013315082C3@wwmess3.bra01.icl.co.uk>
- Reply-To: xsl-list at mulberrytech dot com
Kay Michael wrote:
> It's actually a problem implementing the whitespace-stripping rules when you
> take input from a DOM, since there's a reasonable expectation that the XSLT
> processor shouldn't modify the input tree, and doing whitespace-stripping on
> the fly as you navigate the tree is likely to be incredibly expensive. If
> you supply a DOM as input to Saxon, I copy the whole thing into a new data
> structure (which is also expensive).
So if I have a DOM that's a facade to some other data structure (a
filesystem, or even a database) of non-trivial size, will Saxon run out
of memory?
--
K. Ari Krupnikov
DBDOM - bridging XML and relational databases
http://www.iter.co.il
XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list