I know. I really do want to reduce the points of potential failure and
just want to do the copy at the same point in time and from the same
place as the original file. I think Andrew may be right that I should
do what I had thought of first. I was just testing the waters for
other experiences, to see if there are potential problems (for
example, with garbage collection).
With respect,
Steven
On Jul 8, 2008, at 2:10 AM, Michael Ludwig wrote:
Steven Ericsson-Zenith schrieb:
Okay, well, these are disappointing responses. Especially since much
of the application in this case is written in XSLT (and is processing
and generating a number of collections).
On Jul 8, 2008, at 12:15 AM, Michael Kay wrote:
What is the optimal way to copy a results document?
Write it once from the XSLT stylesheet and then copy it in the
calling application.
Not striving to further disappoint you, but it may be a bit difficult
to understand what you're actually looking for. Making a copy is
essentially open, read/write, close - that's what all the copy
commands
do. It certainly won't get any more efficient or elegant using XSLT.
Michael Ludwig
--~------------------------------------------------------------------
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>
--~--