Altova Mailing List Archives


Re: [xsl] Document function handling POST instead of GET

From: David Carlisle <davidc@--------->
To:
Date: 1/21/2005 5:34:00 PM
> Can i use the same construct for a POST method?

You would have to use an extension function, but even then doing an
operation like POST from a side effect free language like XSLT is
slightly problematic. You have no assurances about the chronological
order in which any templates are evaluated, only that the results
of evaluating the templates are assembled into the final tree in the
correct place. So GET is relatively safe and made safer by the fact
that XSLT specifies that if you get the same URI twice in one transform
you must be returned the same representation (actually stronger the same
node-set)  but tying down the semantics of an update such as POST is
rather trickier.

David

________________________________________________________________________
This e-mail has been scanned for all viruses by Star. The
service is powered by MessageLabs. For more information on a proactive
anti-virus service working around the clock, around the globe, visit:
http://www.star.net.uk
________________________________________________________________________

Disclaimer

These Archives are provided for informational purposes only and have been generated directly from the Altova mailing list archive system and are comprised of the lists set forth on www.altova.com/list/index.html. Therefore, Altova does not warrant or guarantee the accuracy, reliability, completeness, usefulness, non-infringement of intellectual property rights, or quality of any content on the Altova Mailing List Archive(s), regardless of who originates that content. You expressly understand and agree that you bear all risks associated with using or relying on that content. Altova will not be liable or responsible in any way for any content posted including, but not limited to, any errors or omissions in content, or for any losses or damage of any kind incurred as a result of the use of or reliance on any content. This disclaimer and limitation on liability is in addition to the disclaimers and limitations contained in the Website Terms of Use and elsewhere on the site.