Re: [DotGNU]Propoganda starts at home...

[Mason Ham]

Here are my two cents on difference between SOAP and XML-RPC:
1) SOAP attempts to take XML-RPC to the next level by using the XML Scheme
to have more "complex" types than the XML-RPC spec. lets.
2) SOAP tries and solve the namespacing issues with XML-RPC by using
XML-Namespaces.
3) SOAP try's to lay the ground work for the Security of objects ... it will
in the future have things like Authentication in it. The same is true for
both protocols though. They actually use the same mechanisms to achieve it
today ... ie you had pointer in the headers.
4) SOAP is way more difficult for people to learn. That is simply cause you
have to understand all the different types of XML protocols to use it.
XML-RPC is pretty simple to learn. Understand HTTP (both need this),
Understand the XML-RPC types (int,string,float,binary, boolean,
array,struct) and that is pretty much it. The rest is old coding. to be
explicit:

SOAP Payload

<SOAP-ENV:Envelope
  xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/";
  SOAP-ENV:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/";>
   <SOAP-ENV:Body>
       <m:GetLastTradePrice xmlns:m="Some-URI">
           <symbol>DIS</symbol>
       </m:GetLastTradePrice>
   </SOAP-ENV:Body>
</SOAP-ENV:Envelope>


XML-RPC Payload
<?xml version="1.0" ?>
<methodCall>
  <methodName>foo</methodName>
  <params>
    <param>
    <value>
      <struct>
        <member>
          <name>name</name>
           <value><string>John</string></value>
       </member>
       <member>
          <name>age</name>
          <value><int>12</int></value>
       </member>
       </struct>
     </value>
    </param>
   </params>
</methodCall>


for those who want it:
Apache SOAP: http://xml.apache.org/soap/
SOAP Spec: http://www.w3.org/TR/SOAP/

Mason
----- Original Message -----
From: "Jeremy Petzold" <address@hidden>
To: "Myrddian" <address@hidden>
Cc: <address@hidden>
Sent: Friday, July 13, 2001 11:50 PM
Subject: Re: [DotGNU]Propoganda starts at home...


> Myrddian wrote:
>
> >On Sat, Jul 14, 2001 at 11:23:45PM -0400, Mason Ham wrote:
> >
> >>There is an apache soap impl donated by ibm .... problem is the code was
> >>written very hastily and so is tied to tightly together to make it "use"
> >>full unless you that the whole thing (servers and all :-( I have
actually
> >>been thinking about making a whole new "abstract" implementation for it
...
> >>ie one that is modular like the xerces stuff. Till then, I have looked
am
> >>many different home grown ones, and they all either fall short on the
client
> >>or server side (client side marshalling or server side servers). Sorry,
not
> >>trying to be a downer. The upside is that to "get" prototypes done the
> >>apache one is available :-)
> >>
> >
> >It's kind of a problem that we could not start using SOAP, considering
that is
> >what was originally thought to be used.
> >
> >How about XML-RPC, I think SOAP is built on top XML-RPC, any how?
> >ANy body better ideas or something?
> >
> >
> hmmm......I read the W3C doc
at --http://www.w3.org/TR/SOAP/#_Toc478383490--
> and looking at a soap encoded measage, it doesn't seem all that special.
> all it is is a standard way of formating the information in an XML-RPC
> document so that it may be read by an application.  So we can either use
> soap or make our own up like GOAP (GNU Object Access Protocol). it
> wouldn't be that hard.
>
>
> _______________________________________________
> Developers mailing list
> address@hidden
> http://dotgnu.org/mailman/listinfo/developers
>