W3C home > Mailing lists > Public > xml-dist-app@w3.org > February 2003

Re: Difference between SOAP RPC and other BodyContent?

From: Noah Mendelsohn/Cambridge/IBM <noah_mendelsohn@us.ibm.com>
Date: Mon, 24 Feb 2003 11:10:24 -0500
To: "Infoletter" <infoletter@myrealbox.com>
Cc: xml-dist-app@w3.org, xml-dist-app-request@w3.org
Message-ID: <OF7A081210.56F00EFF-ON85256CD7.0058D1AC@lotus.com>
Adonis asks:

>> Is the SOAP application responsible to decide if the 
>> XML-Content is a RPC or is not?

Yes.  In all cases, the SOAP 1.2 ultimate receiver responsible for 
recognizing the contents of the body, and knowing what to do with it.  See 
[1] which says:

An ultimate SOAP receiver MUST correctly process the immediate children of 
the SOAP body (see 5.3 SOAP Body). However, with the exception of SOAP 
faults (see 5.4 SOAP Fault), Part 1 of this specification (this document) 
mandates no particular structure or interpretation of these elements, and 
provides no standard means for specifying the processing to be done.

Whether the RPC convention is used is just one aspect of knowing how to 
deal with the body, and that is always the responsibility of the ultimate 
receiver.  WSDL is one means of establishing agreement between sender and 
receiver on the interpretation of the body, but use of WSDL is not 
required.  You could write some other specification, or call the other 
developer on the phone and tell him or her what's expected.

I hope that clarifies the intention of the SOAP Candidate Recommendation. 
Thank you.


[1] http://www.w3.org/TR/2002/CR-soap12-part1-20021219/#structinterpbodies

Noah Mendelsohn                              Voice: 1-617-693-4036
IBM Corporation                                Fax: 1-617-693-8676
One Rogers Street
Cambridge, MA 02142
Received on Monday, 24 February 2003 11:14:54 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 22:01:22 UTC