|
Scott Sanders
sanders at apache.org
Thu Aug 19 08:39:53 EDT 2004
On Aug 18, 2004, at 7:31 PM, Byron Ellacott wrote: > My main claim here is that XSLT approaches, and any approach that > outputs (correct) XHTML, will always /feel/ slower to the user than > streaming template approaches, because in the first case the entire > document must be available to transform against, and in the second > case the entire document must be parsed before rendering begins. > This is not entirely true. In the java world, I took a Java-based application framework that used DOM and XSLT to do rendering (about 1 page per sec) to a pipelined SAX approach using custom SAX filters instead of DOM, but still using XSLT as the final render, and the application increased performance 100 fold! We could do render in 40ms or less (usually 20). And we also used a streaming approach. Using XSLT in a SAX filter stream allowed use to stream the response, which did increase the perceived performance. Using XSLT does not mean that you cannot stream, because you can. I was using Saxon in that application, BTW, so I know several processors out there can stream. Scott
|