I've asked this on IRC before and Dave Winer's brief comment on the subject made me want to ask here: what advantage does SOAP have over XML-RPC? The latter seems so much easier to me.
RPC is easier, but more limited in what it can do (i.e. SOAP can do RPC, but RPC can not necessarily do SOAP, and RPC was born out of an early draft of SOAP). If RPC works for you, go for it. Though I think SOAP is supported by more environments (e.g..NET), so if that's a concern, then you'll probably have to go that way.
SOAP is a general purpose, object-oriented messaging protocol. It's XML message can be passed through a number of protocols. It is highly generic and allows users to specify new datatypes.
XML-RPC is a narrowly defined RPC mechanism that defines around 10 data types (only about 3 are needed [string, array, struct]), specifies the transport mechanism (HTTP), and has no provisions for user-defined extensions.
I have worked with both in several languages, including Perl, Python, PHP, Java, and C. For those
Couldn't Resist (Score:1)
Sorry. I actually don't know. Someone knowledgeable will undoubtedly explain at some point...
------------------------------
You are what you think.
My understanding (Score:1)
SOAP is an electric toothbrush (Score:1)
SOAP is a general purpose, object-oriented messaging protocol. It's XML message can be passed through a number of protocols. It is highly generic and allows users to specify new datatypes.
XML-RPC is a narrowly defined RPC mechanism that defines around 10 data types (only about 3 are needed [string, array, struct]), specifies the transport mechanism (HTTP), and has no provisions for user-defined extensions.
I have worked with both in several languages, including Perl, Python, PHP, Java, and C. For those
It is a easy choice (Score:2, Insightful)
I decided a long time ago that I am not using anything that Whiner is part of, and that makes me sleep better at night!
sky