Re: Document() function: GET vs. POST

actually I don't see how one could reasonably write a resolver for
http posts, given that one would still want to do http gets. how would
one differentiate between the two? try first as a get, then fall back
to a post? I think to do post basically one would have to do  an
extention function.

Cheers
Bryan Rasmussen

On 12 Nov 2005 08:04:20 +0000, Colin Paul Adams
<colin@xxxxxxxxxxxxxxxxxx> wrote:
> >>>>> "Brian" == granam  <granam@xxxxxxx> writes:
>
>     Brian> The Document() function can do an HTTP GET.
>
> Your assertion is far too strong.
>
> Try: The Document() function might result in an HTTP GET
>         being performed.
> Then add: This is most likely to happen if the URI is an http scheme
>         URI, but it might not happen for such a URI, and it might
>         happen for other URI schems.
>
>     Brian> Could it do an HTTP POST?
>
> Yes.
>
>     Brian> It would be quite useful to be able to interact with web
>     Brian> services which use a more complex HTTP POST interface.  Can
>     Brian> this be done, or is that possibly something for the future?
>
> I presume you meant to say:
>
> "Do any XSLT processors do this now, or is that possibly something for
> the future?"
>
> In which case my answers would be:
>
> 1) Not that I know of, and
> 2) This is of course possible - depending on what you mean by
> interact.
>
> You can probably right a URI resolver to do this.
> --
> Colin Adams
> Preston Lancashire