Altova Mailing List Archives

Re: XML over HTTP: SOAP and ...?

From: David Megginson <david@---------.--->
To: xml-dev@---.---
Date: 3/7/2000 11:46:00 AM
Tom Scola <Thomas.Scola@u...> writes:

> Pardon my naïveté, but I'm having a problem understanding the need
> for so-called "lightweight" protocols such as XML-RPC and SOAP in
> the first place.  If I wanted to write a distributed XML application
> I can:
> 1. Open a socket to a remote system
> 2. Authenticate the connection
> 3. Send and receive XML-encoded data over the socket

Yes, and that's how a lot of people do it.  The potential advantage of
an RPC layer is that it gives a standard way to invoke specific
services on either side, so it's possible to write generic, reusable
higher-level libraries; for example, you could call

  x = y.getSomething();

and not know (or have to know) whether y.getSomething() was a method
on a local object or an HTTP transaction.  Basically, you're adding a
layer of abstraction that takes care of stuff like serializing and
deserializing parameters, looking up services, marshalling (??),
etc. etc.

Sound familiar?  We heard the same thing about CORBA, Java RMI, and
DCOM, among others.  Is it different this time?  Maybe.  Personally,
I'm also happy with simple socket connections for now, but I might
change my mind.

All the best,


David Megginson                 david@m...

This is xml-dev, the mailing list for XML developers.
To unsubscribe, mailto:majordomo@x...&BODY=unsubscribe%20xml-dev
List archives are available at


These Archives are provided for informational purposes only and have been generated directly from the Altova mailing list archive system and are comprised of the lists set forth on Therefore, Altova does not warrant or guarantee the accuracy, reliability, completeness, usefulness, non-infringement of intellectual property rights, or quality of any content on the Altova Mailing List Archive(s), regardless of who originates that content. You expressly understand and agree that you bear all risks associated with using or relying on that content. Altova will not be liable or responsible in any way for any content posted including, but not limited to, any errors or omissions in content, or for any losses or damage of any kind incurred as a result of the use of or reliance on any content. This disclaimer and limitation on liability is in addition to the disclaimers and limitations contained in the Website Terms of Use and elsewhere on the site.