• To: "Joshua Allen" <joshuaa@m...>, "Julian Reschke" <julian.reschke@g...>, <xml-dev@l...>
• Subject: Re: What does SOAP really add?
• From: "Didier PH Martin" <martind@n...>
• Date: Tue, 23 Apr 2002 09:34:18 -0400
• References: <4F4182C71C1FDD4BA0937A7EB7B8B4C104F0566C@r...>

Hi Joshua,

Joshua said:
XSLT document() can't do POST either.  Saying that "all things that do
not use GET are inaccessible to GET", is not informative.  I understood
Paul's position, but I think it's a circular argument.

Didier replies:
Good point. How many times I was stuck with the problem of not being able to
include a document returned from a form request (i.e. an HTTP POST). The
XSLT document function is limited to the HTTP GET and do not support the
different ways to access information through the standard HTTP 1.1. This a
serious limitation is preventing the full benefit of dynamic documents
inclusion. Moreover, it seems that XSLT 2.0 don't even resolve the issue.

cheers
Didier PH Martin

• Follow-Ups:
  • RE: What does SOAP really add?
    • From: "Michael Kay" <michael.h.kay@n...>
  • Re: What does SOAP really add?
    • From: "Thomas B. Passin" <tpassin@c...>
  • Re: What does SOAP really add?
    • From: Alaric Snell <alaric@a...>

• References:
  • RE: What does SOAP really add?
    • From: "Joshua Allen" <joshuaa@m...>

• Prev by Date: Re: What does SOAP really add?
• Next by Date: Re: What does SOAP really add?
• Previous by thread: RE: What does SOAP really add?
• Next by thread: Re: What does SOAP really add?
• Index(es):
  • Date
  • Thread