It's not clear if you want to save it on the client or return it to the
server (I suspect the latter.) If you already have the XML DOM in memory on
the client, then you can send it using an XMLHTTP object, presumably with an
ASP page to receive and handle the contents. (Of course, you have the
original XML + mods, so you could construct and send regardless.)
See MSDN Home > MSDN Library > XML Web Services > XML Core > MSXML 4.0
SDK > DOM Reference
for info on the ixmlhttprequest object and examples.
I'm not sure what they're currently advocating vis a vis .NET, and if others
have more experience with where they're headed I'd like to hear other ideas.
Jeff
Hello-
I am trying to find the slickest way to update an XML tree. Here is
what I am aiming for:
I am using ASP/VBscript to transform the xml/xsl, but I don't want the
ASP/VBscript script to do any manipulations of the XML. The only other
thing I want to use the ASP/VBscript code for is to save the XML file
after it has been manipulated by XSL and/or Javascript.
XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list