| Sign In/My Account | View Cart |
|
|
We've expanded our Perl news coverage and improved our search! Search for all things Perl across O'Reilly!
18.12. Writing an XML-RPC Client18.12.2. SolutionUse the XMLRPC::Lite module from the SOAP-Lite distribution:
18.12.3. DiscussionA single XML-RPC server may run many services, differentiated by their method name: ClassName.handler corresponds to ClassName->handler on the server side; A.B.method corresponds to A::B->method; and a call to handler corresponds to main->handler. The proxy is the actual URL of the server. If you're using a CGI server, the proxy method looks something like this:
There are three ways to invoke remote methods. The first way is to use the call method on your XMLRPC::Lite object. The first argument to call is the remote method name, and the remaining arguments are parameters for the remote method:
The second way to invoke a remote method is to call that method on the XMLRPC::Lite object. This works only when the remote method name isn't the same as a method provided by the XMLRPC::Lite object. For example:
The last way to invoke a remote method is with autodispatch, turning unrequired function calls and method invocations in your Perl program into XML-RPC requests. Enable autodispatch with:
A critical difference between autodispatch and the other styles is that autodispatch automatically decodes the result into a Perl value for you. When you use an XMLRPC::Lite object, you must explicitly invoke the result method to decode the XML-RPC response into a Perl value. View the past week's recipes: Today | Yesterday | 3 days ago | 4 days ago | 5 days ago | 6 days ago | A week ago
|
|
Sponsored By: |