XMLRPC is the acronym of Extensible Markup Language - Remote Procedure Call. An XML specification that describes the mechanism of remote procedure calling using XML. Can be said, is one of the XMLRPC webservice simplified form of the conventional standard. Two systems that are truly separate and different platforms and environments can communicate with each other through means of an XML file.
Communications protocol used is standard protocol, the most popular in the world: HTTP. Request that is sent via HTTP POST method should be used. Procedures that will be called with its parameters wrapped in an XML file in XMLRPC specification. Similarly, the return value is, before the first post will be wrapped in the form of XML and transferred over the HTTP protocol traffic on the internet.
Big picture can be explained simply in the picture below:
Specifications made by the team XMLRPC is quite complete, for example, how do I send a parameter and return the return value. Include XMLRPC standard data type is also included.
XMLRPC implementation specification has been applied widely in various programming environments. In Java itself, from the Apache team has made the library compliance with the specifications XMLRPC. This is easier for us to not need to fuss in the deal such as low-level parser to process the data from the XML. All was wrapped in a higher level in the form of class-class library. For example, each object java.util.Date akan converted to type standard XMLRPC data automatically. And more convenience-ease of the other.
Currently, some services have been popular support XMLRPC. The most light, of course, is blogging service. Now every machine mutual blog to communicate with one another (Trackback, pingback) using standard XMLRPC. XMLRPC with this, several new services to manage the blog outside of the standard software appears. Examples are WordPress and Blogger API API. Now we can write a blog post with a desktop-based software (Microsoft Word 2007 can do so) without having to first connect to the internet.
Will XMLRPC akan developed as an alternative to the standard of the existing types of SOAP, UDDI, and WSDL? We wait.
Communications protocol used is standard protocol, the most popular in the world: HTTP. Request that is sent via HTTP POST method should be used. Procedures that will be called with its parameters wrapped in an XML file in XMLRPC specification. Similarly, the return value is, before the first post will be wrapped in the form of XML and transferred over the HTTP protocol traffic on the internet.
Big picture can be explained simply in the picture below:
Specifications made by the team XMLRPC is quite complete, for example, how do I send a parameter and return the return value. Include XMLRPC standard data type is also included.
XMLRPC implementation specification has been applied widely in various programming environments. In Java itself, from the Apache team has made the library compliance with the specifications XMLRPC. This is easier for us to not need to fuss in the deal such as low-level parser to process the data from the XML. All was wrapped in a higher level in the form of class-class library. For example, each object java.util.Date akan converted to type standard XMLRPC data automatically. And more convenience-ease of the other.
Currently, some services have been popular support XMLRPC. The most light, of course, is blogging service. Now every machine mutual blog to communicate with one another (Trackback, pingback) using standard XMLRPC. XMLRPC with this, several new services to manage the blog outside of the standard software appears. Examples are WordPress and Blogger API API. Now we can write a blog post with a desktop-based software (Microsoft Word 2007 can do so) without having to first connect to the internet.
Will XMLRPC akan developed as an alternative to the standard of the existing types of SOAP, UDDI, and WSDL? We wait.
No comments:
Post a Comment