XML-RPC vs. SOAP¶
XML-RPC¶
SOAP¶
Porovnani¶
- http://weblog.masukomi.org/writings/xml-rpc_vs_soap.htm
- http://www.cs.rpi.edu/~hollingd/netprog/notes/soap-xmlrpc/soap-xmlrpc.pdf
| Vlastnosti | XML-RPC | SOAP |
| Basic scalars | yes | yes |
| Structs | yes | yes |
| Arrays | yes | yes |
| Named structs and arrays | no | yes |
| Detailed fault handling | yes | yes |
| Short learning curve | yes | no |
| Developers specified character set | no | yes (US-ASCII, UTF-8, UTF-16) |
| Developer defined data types | no | yes |
| Can specify recipient | no | yes |
| Require client understanding | no | yes |
| Message specific processing instructions | no | yes |
When you get right down to it XML-RPC is about simple, easy to understand, requests and responses. It is a lowest common denominator form of communication that allows you to get almost any job done with a minimum amount of complexity. SOAP, on the other hand, is designed for transferring far more complex sets of information. It requires profuse attribute specification tags, namespaces, and other complexities, to describe exactly what is being sent. This has its advantages and disadvantages. SOAP involves significantly more overhead but adds much more information about what is being sent. If you require complex user defined data types and the ability to have each message define how it should be processed then SOAP is a better solution than XML-RPC (be sure to check out language specific solutions to this problem like java's RMI ( http://java.sun.com/products/jdk/rmi/ )). But, if standard data types and simple method calls are all you need then XML-RPC will give you a faster app with far fewer headaches.
Vysledek¶
Pro potreby projektu Warden byl vybran komunikacni protokol SOAP:- jednoduche zajisteni bezpecnosti prenasenych dat pomoci zabaleni do TLS/SSL
- jednoducha implementace pomoci Perl modulu
- podobny objem prenasenych dat jako je u XML-RPC
- novejsi podoba XML-RPC