RE: Issue with soap-rpc:result

I can confirm that the idea that "RPC is just an optional layer above 
SOAP" has always been the opinion of at least this author of SOAP 1.1.

-----Original Message-----
From: Jacek Kopecky [] 
Sent: Friday, February 15, 2002 5:52 AM
To: Tim Ewald
Subject: RE: Issue with soap-rpc:result

Tim, please see my replies below.

                   Jacek Kopecky

                   Senior Architect, Systinet (formerly Idoox)

 > > I had originally seen SOAP 1.1 as being closer to #2. I now 
 > > see lots of 
 > > discussion and proposed text that seems to presume model #1.  
 > > We seem to 
 > > be freely talking about "interfaces" (an endpoint construct), or
 > > Gudge's note:
 > > 
 > > "For example, given the following COM IDL method signature:
 > > 
 > >         void Add ( [in] long x, [in] long y, [out] long* sum );"
 > > 
 > > which is very much an option #1 way of looking at the world.
 > I think *loads* of people think of not just the SOAP RPC model, but
 > as a whole this way.

I for myself learned SOAP starting with version 1.1 and it seemed 
to me from the start that RPC is just an optional layer above 
SOAP. But I don't have enough statistical information to be able 
to contradict your sentence above, therefore it may be useful to 
try to stress this point in the spec. I think this was attempted 
already, if only by calling the RPC convention an adjunct.


Received on Saturday, 16 February 2002 23:12:39 UTC