W3C home > Mailing lists > Public > xml-dist-app@w3.org > July 2001

[RPCTF] RPC as an application or an extension of SOAP?

From: Jacek Kopecky <jacek@idoox.com>
Date: Fri, 20 Jul 2001 19:35:00 +0200 (CEST)
To: <xml-dist-app@w3.org>
Message-ID: <Pine.LNX.4.33.0107201845540.30885-100000@bimbo.in.idoox.com>
 Hi, on the RPC task force telecon I recalled that during the
February face-to-face meeting the following issue arose and I
don't remember it ever being resolved:
 Is RPC an extension of SOAP or is it an application of SOAP?
 Let me show what I see as the meaning by this difference:
 1) if RPC is an extension of SOAP it should be able to live
happily in SOAP headers (which it doesn't in SOAP/1.1), and we
should be able to create messages that use RPC but whose main
purpose would be something different.
 2) if RPC is an application of SOAP (in other words RPC is a
description of how to use SOAP in certain situations), we have
"RPC messages" - messages whose main purpose is to invoke a
method or communicate its result. There would be no messages that
use RPC and are not "RPC messages".

 Personally, I can't understand RPC as a module. RPC uses SOAP to
do some semantics. I can't see how RPC could _extend_ the
semantics of something else.

 Please the proponents of the RPC-as-a-module view write what
your thinking is.

                            Jacek Kopecky

Received on Friday, 20 July 2001 13:35:02 UTC

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