But does Saxon occupy more memory
than Xalan (I don't know if Saxon implements DTM) ?
Both Saxon and Xalan implement their own proprietary internal data structure for storing the XML source. Saxon's implementation (the "tinytree") is smaller and generally faster for common cases than Xalan's. But then, Xalan can almost work directly off a JAXP DOM, while Saxon always has to built its own internal representation. Also, Xalan has a "streaming mode", which builds the internal tree only as needed. Once fully implemented, optimized and enhanced with the capability of discarding branches which are no longer needed, this may enable some classes of transformations on arbitrarily large input. Ask on the Xalan list for details.
Still, Saxon uses 3..5 times the size of the input in memory.
J.Pietschmann
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
