- From: <bugzilla@jessica.w3.org>
- Date: Thu, 13 Feb 2014 09:59:05 +0000
- To: public-qt-comments@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=24648
Bug ID: 24648
Summary: Streamability of unparsed text
Product: XPath / XQuery / XSLT
Version: Last Call drafts
Hardware: PC
OS: Windows NT
Status: NEW
Severity: normal
Priority: P2
Component: XSLT 3.0
Assignee: mike@saxonica.com
Reporter: abel.online@xs4all.nl
QA Contact: public-qt-comments@w3.org
While I realize this subject is not new, it came up on the XSL List and Dimitry
Novatchev sent me a direct note pointing to it:
http://www.biglist.com/lists/lists.mulberrytech.com/xsl-list/archives/201401/msg00019.html.
The points raised in this discussion are:
1) large text nodes are not streamable (consider a large base64 chunk)
2) externally resourced unparsed-text is not streamable, only if you are lucky
enough that unparsed-text-lines is processed using streaming, but the function
itself is stable, so buffering the whole input can be required.
Dimitry expressed his concern about both. I think we only need to address the
second point, in the sense that we should allow something similar to:
<xsl:stream unparsed-text-lines="http://example.com/largetext.txt">
<!-- each context item here is a line and is grounded -->
</xsl:stream>
The analysis of this is simple enough, the use-case is to allow multiple reads
to be non-deterministic.
--
You are receiving this mail because:
You are the QA Contact for the bug.
Received on Thursday, 13 February 2014 09:59:07 UTC