Re: Heads up: A key difference between SOAP and XML-RPC

[Dave Winer <dave@userland.com>]

This was one of the key issues in the Busy Developer's Guide and on the soapbuilders list over the last few days. There was no way to interpret the SOAP 1.1 spec to allow for the XML-RPC convention, so we basically broke our implementation. The breakage in Frontier/Radio is documented on the page I pointed to. The docs we write will still work for both dialects, but they will have to be written more carefully. Truth be told, there hasn't been a lot of deployment of SOAP in our world yet, because interop has been so elusive. So this change will be somewhat annoying, but that's life. Dave

 

 

----- Original Message -----

From: Mike.Champion@SoftwareAG-USA.com

To: xml-dev@lists.xml.org

Sent: Saturday, March 31, 2001 11:02 AM

Subject: RE: Heads up: A key difference between SOAP and XML-RPC

 

-----Original Message-----
From: Dave Winer [mailto:dave@userland.com]
Sent: Saturday, March 31, 2001 1:45 PM
To: soapbuilders@yahoogroups.com; xml-rpc@egroups.com; XML-Dev (E-mail); xml-dist-app@w3.org
Subject: Heads up: A key difference between SOAP and XML-RPC

After a little head-bashing and then smoke-clearing, this became apparent.

 

1. In SOAP, procedures take named parameters and order is irrelevant.

 

2. In XML-RPC order is relevant and parameters are not named. 

 

To what extent does this account for the interoperability problems that have been discussed on the mailing lists?  What's the effect on the Busy Developer's Guide?