Supporting SOAP, XML-RPC, XML over HTTP in web services
I am writing a chapter in a new Java book this week that covers XML-RPC, XML over HTTP, and SOAP.
I use all three options myself, so writing this material is fun and not too difficult.
However, now I am thinking of the pros and cons of having three communications options for web services. All three options that I am covering are different, and have their specific uses.
SOAP is the most general purpose of the three, but it is also heavy weight. On the other hand, libraries to support XML-RPC are simple and easy to use. Using XML over HTTP is very simple.
Does having so many options fracture the market and technology space? Perhaps, but options are good. SOAP will be the "winner" for large scale web services because of its standardization and associated technologies like WSDL and UDDI. Still, I like simpler options for smaller scale systems.
6:48:46 AM 
|
