I had even gotten to the point of hacking Tomcat and the servlet API to support threading and pipes between tags, only to find that Java pipes are fundamentally flawed (or broken, depending on your point of view). Amazing and quite unforgivable given that Java comes from a Unix company.
And the Tomcat servlet filtering API is also fundamentally (and surprisingly) based on single-threading and buffers. Very disappointing.
So three cheers for SAX pipelining for Fop!
Oh, and BTW in another context I have timed using DOM trees vs XML strings as intermediate data to feed Xalan, and there was no difference that I could measure. May DOM disappear from the face of the earth.
Joerg Pietschmann wrote:
[EMAIL PROTECTED] wrote:
some comments to Joergs message: I do not think using TraxInputHandler or XSLTInputHandler is better than using a DOM tree.
Just for clarification: i did not recommend temporary files over intermediate DOM trees. I recommend a SAX event stream over any of temporary files, intermediate in-memory buffers for serialized XML or intermediate DOM trees. A DOM tree is often still preferable over some serialization because of performance (no reparsing) but not necessarily because of memory consumtion (depends on the implementation).
