what is XMLRPC

XML RPC is a easiest way to kick start writing of Web Services, where applications "talk" across networks (intranets or internet) .
Creating an XML-RPC Web service with Perl is almost as easy as CGI scripting. This blog is a tutorial on using XML RPC with Perl. It uses Perl's Frontier::RPC library to create simple clients and servers.
WHAT IS RPC?Remote Procedure Call (RPC) is a mechanism to call functions Remote Procedure Calls (RPC) are not a new concept they have been in Unix class oses for a long time and on Windows OS too. A client/server system, RPCs have traditionally been procedures called in a program on one machine that go over the network to some RPC server that actually implements the called procedure.
The RPC server bundles up the results of the procedure and sends those results back to the caller. The calling program then continues executing. While this system requires a lot of overhead and latency, it also allows less powerful machines to access high powered resourcesWHAT IS XML RPC? A RPC call earlier was to be sent in propritery formats that can be understood only by the specific client and the server. With the evolution of XML as a standard for information interchange.XML can be used to encode RPC Calls and use it in communication.an implementation of XML RPC would be as follows a client accessing a server encodes it's request into XML and uses simple HTTP protocol to transfer the XMLAt the server side the XML is parsed and procedure are called with parameters that came from the client.
The exciting part about XML-RPC is that it can cross programming language and operating system platforms, allowing clients and servers written in different languages to work together. Perl clients can talk to Java servers; Python listeners can service PHP requests; you can even write XML-RPC programs in bad, old C.
XML-RPC is extremely easy to work with because the details of the XML translations are hidden from the user, unless, of course, you are implementing your own XML-RPC library. There are two important aspects of this protocol that you should keep in mind when building your middleware. XML-RPC is built on HTTP and, like ordinary Web traffic, its stateless conversations are of the request and response variety.
There is no built-in support for transactions or encryption. The other important detail to remember is that XML-RPC has a finite set of datatypes. Client procedure arguments and listener return values are mapped in a non-extendable XML subset. In practice, though, XML-RPC's datatypes are often flexible enough to do complex tasks. The XML RPC Data Types:XML-RPC tag Description a sequence of characters signed or unsigned 32-bit integer values true(1) or false(0) signed double precision floating point numbers date and time (but no timezone) a base64 encoded string a container for a sequence of datatypes a container for key-value pairs XML RPC is a good mechanism to start writing Web Services, a more modern refined brother of XML RPC is SOAP.