Quick Contact:
Enter verification code
top img
Partners

Flash web design

Flash based website design company.

Website design company

Affordable website design company to outsource your design and dynamic web application needs.

Web design resources

Web design and related resources

Bangladesh website hosting

Quality linux, cpanel hosting solution from Bangladesh

 

PHP Tips:

SOAP and XML-RPC Compared:


The choice of which RFC protocol to implement—SOAP or XML-RPC—is often dictated by circumstance. If you are implementing a service that needs to interact with existing clients or servers, your choice h«: already been made fur you. For example, implementing a SOAP interface to your Web log might be interesting, but might not      provide integration with existing tools. If you want to query the Amazon or Google If-search APIs, the decision is not up to you: You will need to use SOAP.

If you are deploying a new service and you are free to choose which protocol to use, you need to consider the following:

• From an implementation standpoint, XML-RPC requires much less initial work than SOAP.

• XML-RPC generates smaller documents and is less expensive to parse than SOAP.

• SOAP allows for user-defined types via Schema. This allows both for more robust data validation and auto-type conversion from XML to PHP and vice versa. In XML-RPC, all nontrivial data serialization must be performed manually.

• WSDL is cool. SOAP's auto-discovery and proxy-generation abilities outstrip those of XML-RPC.

• SOAP has extensive support from IBM, Microsoft, and a host of powerful dot-coms that are interested in seeing the protocol succeed. This means that there has been and continues to be considerable time and money poured into improving SOAP's interoperability and SOAP-related tools.

• SOAP is a generalized, highly extensible tool, whereas XML-RPC is a specialist protocol that has a relatively rigid definition.

I find the simplicity of XML-RPC very attractive when I need to implement an RFC that I control both ends of. If I control both endpoints of the protocol, the lack of sound auto-discovery and proxy generation does not affect me. If I am deploying a service that will be accessed by other parties, I think the wide industry support and excellent sup­porting tools for SOAP make it the best choice.