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

Paul Prescod wrote:

>Already, Microsoft's GET and POST bindings
>demonstrate that you can get *exactly the same* XML type mappings
>without using SOAP. And if you aren't interested in pre-declared types,
>XML-RPC is more reliably interoperable in my experience than SOAP.
>
Respectfully, I'd say that Microsoft's GET and POST bindings demonstrate 
exactly the opposite - that as soon as you use any parameter structure 
less trivial than a name/value list, VS.NET uses SOAP instead.

Francis.

• Follow-Ups:
  • 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...>

• Prev by Date: Re: W3C Culture and Aims (Was: 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