[XML-DEV Mailing List Archive Home] [By Thread] [By Date] [Recent Entries] [Reply To This Message]

Re: What does SOAP really add?

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

Paul Prescod wrote:

>Francis Norton wrote:
>
>>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. 
>>
>
>I didn't mean to imply otherwise. The term "bug" was correct from the
>point of view of the spec, but it probably not really an implementation
>bug. Clearly they've decided to support some parts of the WSDL/HTTP
>binding and not others. Perhaps it was one of those not-enough-time
>issues.
>
Anyone know how difficult it would be to implement a server that 
accepted mime-encoded HTTP POST requests? The C# documentation appears 
to suggest it should be supported by the HttpRequest object, in which 
case it should be trivial. It seemed a bit weird to me, but that may 
just be my lack of experience this close to the wire.

>>.... 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.
>>
>
>Although this would technically work, I agree that this is a misuse of
>POST. But no less a misuse if you wrap it in SOAP:Envelope elements!
>
Yep, I was being picky. I was a SOAP + Schema supporter when SOAP 
appeared to solve my XML parameter problems in a way that url-encoded 
POSTs couldn't (and mime on input never to me), but I now see WSDL + 
 Schema as a more relevent resolution to my requirements, and I'm moving 
towards transport agnosticism. [But didn't the ancient Greeks have a 
penalty for those who took no part in matters of great controversy? 
Their spirit lives on in xml-dev!]

Francis.

• Follow-Ups:
  • Re: What does SOAP really add?
    • From: "Dave Winer" <dave@u...>
  • RE: What does SOAP really add?
    • From: Bill de hÓra <dehora@e...>

• 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...>
  • 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: W3C Culture and Aims (Was: What does SOAP really add?)
• Next by Date: RE: W3C Culture and Aims (Was: What does SOAP really ad d?)
• Previous by thread: Re: What does SOAP really add?
• Next by thread: RE: What does SOAP really add?
• Index(es):
  • Date
  • Thread