As John says XML-RPC actually predates SOAP. It's also simpler and thus
easier to implement but SOAP has better support for handling complex types.
Ultimately you have to choose the one that best meets your application
requirements. I do feel strongly that HTTP is the wrong transport protocol
On Fri, 11 Oct 2002 09:45:39 CDT, Ward Harold said:
requirements. I do feel strongly that HTTP is the wrong transport protocol
for an RPC mechanism; BEEP is a much better choice.
HTTP has the advantage of usually being passed by firewalls.
Now take a deep breath and ask yourself What's wrong
Timur Shemsedinov wrote:
Here question, whether is necessary to have two
realizations of the RPC using XML?
Again, it's not up to the IETF; XML-RPC already exists. And, in fact,
it predates SOAP.
--
/===\
|John Stracke
On 10/11/02, Ward Harold wrote:
As John says XML-RPC actually predates SOAP. It's also
simpler and thus easier to implement but SOAP has better
support for handling complex types. Ultimately you have to
choose the one that best meets your application
requirements.
p.s. RFC 3288 describes how
