Re: Document function handling POST instead of GET

I want to use POST in a idempotent (how like that word!) way, thus i
have no side-efects here. The problem is i probably will have lots of
data to pass, longer than can fit in a URL. Specifically to my
problem, i want to pass SQL SELECT clauses tha can be somewhat big,
and also connection strings.

Can there be a simpler solution?


Thanks.

On Fri, 21 Jan 2005 17:33:40 GMT, David Carlisle <davidc@xxxxxxxxx> wrote:
> 
> > 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
> ________________________________________________________________________