Daniel L. Rall wrote: >>I'm in the situation that I manually need to create/encode/decode and >>dispatch XML-RPC requests and responses. Encoding/decoding stuff was a > > Can you tell us more about why you want to do this?
I'm using an ESB called Mule (http://mule.codehaus.org/) for a distressingly distributed and asynchronous project where I need to integrate a server that is only accessible via perl API. Since I only need a few well-defined calls and didn't want to start with all the SOAP armwaving, I decided to use XML-RPC for that. Mule automatically routes messages over various transports, and I wanted to create new xmlrpc:// transport plugin so that a message started on a Java client sent to a local vm:// endpoint could be transformed (encoded, compressed, whatever..), forwarded via HTTP to a server instance which does some more processing (other systems via JMS are involved), and eventually ends up in the perl server to trigger an action. Also the perl server is supposed to send response events to another Java VM (running mule), and again I figured it would be easiest to just use XML-RPC as transport for the endpoint. Holger
