I'm having trouble understanding the restriction that
one cannot read from and write to the same URI during
a single transformation. This prohibits the common (i
would think) 'use' case where one wants to overwrite a
file with a slightly modified version of the same
file. For example, one wants to update a list of
contacts with one more contact.
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?
(Please note that I am *not* advocating writing to the
same document more than once in a single
transformation. That inherently relies upon order of
execution.)
Steven
____________________________________________________________________________________
Yahoo! Music Unlimited
Access over 1 million songs.
http://music.yahoo.com/unlimited
--~------------------------------------------------------------------
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>
--~--