CORBA/RMI vs XML/RDF/XMI
jlapp at webMethods.com
Tue Jan 18 20:28:33 GMT 2000
At 03:10 PM 1/18/00 -0500, David Megginson wrote:
>Miles Sabin <msabin at cromwellmedia.co.uk> writes:
> > I'm having trouble seeing why XML over HTTP is preferable to
> > eg. CORBA or Java RMI (maybe tunneled through HTTP if there's
> > a need to traverse firewalls) for application specific comms.
> > How is application specific markup better than an application
> > specific binary wire protocol?
>[...] In other words
> Intranet = good connectivity = few users = stateful = CORBA/RMI
> Internet = bad connectivity = many users = stateless = XML/RDF/XMI
I think the #1 reason is probably barrier to entry. You can get an
HTTP stack and an XML parser for pretty much anything, and you can get
HTTP and XML through pretty much anything (such as
firewalls). Learning curves and deployment times tend to also be shorter.
CORBA requires tightly-coupled software at both ends. RMI rides on the
pervasiveness of Java, but both RMI and CORBA require HTTP tunneling to
get through firewalls -- just another piece that XML/HTTP doesn't require.
Besides, the smaller a piece is, the easier it is to swallow.
xml-dev: A list for W3C XML Developers. To post, mailto:xml-dev at ic.ac.uk
Archived as: http://www.lists.ic.ac.uk/hypermail/xml-dev/ or CD-ROM/ISBN 981-02-3594-1
Please note: New list subscriptions now closed in preparation for transfer to OASIS.
More information about the Xml-dev