NOTE: use Perl; is on undef hiatus. You can read content, but you can't post it. More info will be forthcoming forthcomingly.
All the Perl that's Practical to Extract and Report
In the near future, the probability is close to zero. In the distant
future, I'll be dead, and posterity can do whatever they like... :-) --lwall
Stories, comments, journals, and other submissions on use Perl; are Copyright 1998-2006, their respective owners.
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 projects for which you own both sides of the RPC transaction, XML-RPC is simple and reliable. It's even easy to bend XML-RPC into unexpected places like SMTP and unix domain sockets.
SOAP messages are necessarily complex XML messages. XML-RPC message are so simple, the DTD came after the spec and several language implementations.
I use SOAP only when I have too.
Reply to This