On 9/20/05, Cooper Stevenson <[EMAIL PROTECTED]> wrote: > XML-RPC of course! > http://www.xmlrpc.com/ > Fred James wrote: > > > Questions (forgive me if they are dumb ones) > > (a) What is required to send, and receive, an XML message?
The ability to create a socket and the client libraries you need to marshal and unmarshal your data > > (b) Is it required to have a web server running on the originating > > server (home of my interface)? No. you are creating a client application that sends a request and gets a response. >From what you've said it sounds like XML-RPC would be a good choice and it's easy to find prepackaged libraries for any language in current use. Now if your requirements were somewhat different (say non-blocking sockets, many small exchanges per transaction, etc.) xml over http might not be the right answer. and of course if you are dealing with predefined xml documents then xml-rpc is NOT what you want, since it is only defining the message and not the content. _______________________________________________ EUGLUG mailing list [email protected] http://www.euglug.org/mailman/listinfo/euglug
