On Fri, 11 Oct 2002, Ward Harold wrote: > As John says XML-RPC actually predates SOAP. It's also simpler and thus > easier to implement but SOAP has better support for handling complex types. > Ultimately you have to choose the one that best meets your application > requirements. I do feel strongly that HTTP is the wrong transport protocol > for an RPC mechanism; BEEP is a much better choice. HTTP and BEEP aren't transport protocols. session and transfer protocols, perhaps. Since they both run over TCP, they're both completely wrong for RPC. L. XMLRPC - it's not XML, and it's not RPC. <http://www.ee.surrey.ac.uk/Personal/L.Wood/><L.Wood@ee.surrey.ac.uk>