xsl-list
[Top] [All Lists]

Re: XALAN-FOP Performance and Push-Pull Processing

2005-01-18 13:54:50

Is more memory used because of
Anyone who's followed this list for a day or two will tell you that I'm
reasonably reliable for answers concerning XSLT programming but
distinctly unreliable for any aspects of implementation:-) However
pretty much all current XSLT processors slurp up the entire document
before starting so the major memory cost is already used up before any
processing starts.

Are XSLT processors such as Saxon or XALAN built with anything
internal that determines the processing based on something as simple as
Push or Pull, or anything else?

I defer to those who have implemented a processor (or opened up the
source zip files to look at the implemntations) There are plenty of such
people on the list. 

David

________________________________________________________________________
This e-mail has been scanned for all viruses by Star. The
service is powered by MessageLabs. For more information on a proactive
anti-virus service working around the clock, around the globe, visit:
http://www.star.net.uk
________________________________________________________________________

--~------------------------------------------------------------------
XSL-List info and archive:  http://www.mulberrytech.com/xsl/xsl-list
To unsubscribe, go to: http://lists.mulberrytech.com/xsl-list/
or e-mail: <mailto:xsl-list-unsubscribe(_at_)lists(_dot_)mulberrytech(_dot_)com>
--~--



<Prev in Thread] Current Thread [Next in Thread>