Thanks.
But when the source is SAXSource, Xalan still needs to build an internal
DTM for the tree representaion, right? I read somewhere that current
SAX2DTM doensn't save much in terms of memory. And DOM2DTM only wraps a
DTM around the existing DOM -- does it not save the time of building the
DTM, since it already had the tree?
Let's assume the incremental mode is turned off or doesn't contribute
much, because the stylesheet needs to scan the whole XML for
transformation.
-----Original Message-----
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]
Sent: Monday, July 16, 2001 11:36 AM
To: [EMAIL PROTECTED]
Cc: [EMAIL PROTECTED]
Subject: RE: Speed?
>1. XML file --> SAX parser --> SAX Source --> Xalan
>2. XML file --> DOM parser --> DOM Source --> Xalan
>Which approach will be faster, or less memory?
At this time, I think #1 will win on both counts.
