Re: Why does copy transform take so long?

[Joseph Kesselman]

Xalan should be noticably more efficient when processing from a SAX or
stream source (ie, when you let it build a DTM) than when processing from a
DOM.

Similarly, Xalan's native output is SAX. If you want to both serialize and
further process, you might want to consider a SAX "tee" fitting  -- a SAX
stage which routes its input both to a serializer and to additional
processing -- rather than building a DOM tree.

None the less, your performance should be better than what you're
reporting, unless you're in a situation where you're swapping yourself to
death...

______________________________________
Joe Kesselman, IBM Next-Generation Web Technologies: XML, XSL and more.
"The world changed profoundly and unpredictably the day Tim Berners Lee
got bitten by a radioactive spider." -- Rafe Culpin, in r.m.filk


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]