DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT <http://nagoya.apache.org/bugzilla/show_bug.cgi?id=1083>. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE.
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=1083 OutputStream or Writer inside StreamResult always get flushed by Transformer.transform() [EMAIL PROTECTED] changed: What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |CLOSED ------- Additional Comments From [EMAIL PROTECTED] 2003-08-13 14:52 ------- Closing this bug down. We are not changing the internal flushing behavior of the serializer. This is a performance concern, not a problem with functionality. That said, since the last append to this bug much work has gone into improving the performance of the serializer now used by both Xalan-J interpretive and XSLTC. The analysis showed that flushing at endDocument() was not seen to be a performance issue, although other things were. It isn't the 1000 times faster that one dreams about but typically ranges from a few percent, to a more common 30% faster and in some special cases much more than that. Of course it all depends on the input XML and stylesheet. Regards, Brian Minchau
