Please see
http://www.w3.org/TR/xslt-21/#streaming-concepts
"Streaming achieves two important objectives: it allows large documents
to be transformed without requiring correspondingly large amounts of
memory; and it allows the processor to start producing output before it
has finished receiving its input, thus reducing latency."
Michael Kay
Saxonica
On 14/08/2010 12:51, Costello, Roger L. wrote:
Hi Folks,
In what I've read, the main benefit of the streaming capability in XSLT 2.1 is
memory. Namely, an XSLT processor won't have to hold in memory a representation
of the entire XML document.
> From the reading that I have done on streaming in general (i.e., not
XSLT-specific), I get the impression that the main benefit of streaming is that it
enables processing before the complete set of data is available. For example, a
series of deposits and withdrawals to a bank account over a period of time is a
stream. A stream-based program would be long running and would process the
deposits and withdrawals as they occur. Notice in this example, the key issue is
incremental processing of data as the data arrives; the key issue is not one of
memory (in fact, memory isn't even an issue).
QUESTION
Is the streaming capability in XSLT 2.1 just for dealing with large XML
documents or will it support data that arrives in bits and pieces (i.e.,
streamed data)?
/Roger
--~------------------------------------------------------------------
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>
--~--
--~------------------------------------------------------------------
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>
--~--