• To: Paul Prescod <paul@p...>
• Subject: Re: What does SOAP really add?
• From: Francis Norton <francis@r...>
• Date: Mon, 22 Apr 2002 14:29:46 +0100
• Cc: xml-dev@l...
• References: <4F4182C71C1FDD4BA0937A7EB7B8B4C104F0543F@r...> <3CC35EE7.84673694@p...> <3CC3EEB4.3080902@r...> <3CC3FDB7.B5256315@p...>
• User-agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:0.9.9) Gecko/20020311

Paul Prescod wrote:

>Nevertheless, there is no reason that the same should not work for
>input. VS.net merely has a bug that does not permit that. If one uses
>HTTP POST there is no apparent reason that anything that can be done on
>OUTPUT should be restricted on INPUT. It seems quite simple to me:
>
Two problems with this - first, the the bug  appears to extend to the 
 implementation of mime for input - at least, I can telnet a 
application/x-www-form-urlencoded POST to my VS.Net application, but not 
a text/xml one. Could be operator malfunction, of course, and I agree 
that the WSDL note appears to permit this idiom. But secondly, the the 
parameters for my transaction are in fact for a database query, which  
HTTP 1.1 appears to say [1] is an incorrect use of POST.

Francis.

[1] http://www.w3.org/Protocols/rfc2616/rfc2616-sec9.html#sec9.5

• Follow-Ups:
  • Re: What does SOAP really add?
    • From: Mark Baker <distobj@a...>
  • Re: What does SOAP really add?
    • From: Paul Prescod <paul@p...>

• References:
  • RE: What does SOAP really add?
    • From: "Joshua Allen" <joshuaa@m...>
  • Re: What does SOAP really add?
    • From: Paul Prescod <paul@p...>
  • Re: What does SOAP really add?
    • From: Francis Norton <francis@r...>
  • Re: What does SOAP really add?
    • From: Paul Prescod <paul@p...>

• Prev by Date: Re: What does SOAP really add?
• Next by Date: Re: W3C Culture and Aims (Was: 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