xsl-list
[Top] [All Lists]

RE: [xsl] Reading from and writing to the same URI (XTRE1500)

2006-11-14 11:07:54
To preempt the argument that ordering becomes an issue 
(namely, did the read occur before or after the write), I'll 
reiterate a sentiment posted in a thread to this forum.  Put 
a stake in the ground and say that all writes occur at the 
end of the transformation. 
All reads see the documents prior to modification.  Is there 
a flaw in this reasoning that necessitated this restriction? 

This would require an implementation to hold the result tree in memory (it
might be gigabytes) just in case the stylesheet decides to read the old
version of the file. A lot of cost to everyone providing a small benefit to
a few.

(In practice you can generally get around the restriction - at your own risk
- by using two different URIs that refer to the same underlying file.)

Michael Kay
http://www.saxonica.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>
--~--