You are viewing a plain text version of this content. The canonical link for it is here.
Posted to soap-user@xml.apache.org by Tung Mansfield <ma...@orbitcommerce.com> on 2000/11/17 17:08:42 UTC
RMI versus SOAP
What are the pros and cons of RMI versus SOAP? I am particularly interested
in the performance difference between the two. I am assuming the
communication is between two systems from two different companies where the
communication will most likely be through HTTP. Is RMI over HTTP still
faster than SOAP?
RE: RMI versus SOAP
Posted by Filip Hanik <fh...@pakana.com>.
Hi David,
what about IIOP and CORBA.
You can achieve language independence with a speed faster than both RMI and
SOAP.
However, as stated in the article I replied with earlier. SOAP can be very
useful since it can run on almost any protocol.
you run it on HTTP if you have firewall problems, you can run it on
SMTP/POP3 using email. very cool actually
Filip
Filip Hanik
Technical Architect
Pakana Corporation
fhanik@pakana.com
415-371 9200 ext 3529
-----Original Message-----
From: dhicks [mailto:dhicks]On Behalf Of David C. Hicks
Sent: Friday, November 17, 2000 10:55 AM
To: soap-user@xml.apache.org
Subject: Re: RMI versus SOAP
In my own mind, the primary reason for choosing SOAP over RMI is that
SOAP is a language independent protocol. With RMI, you have to assume
that you have Java on both sides. With SOAP, I can have a Java-based
client talking to a C++ server...or basically any combination of
languages that I choose. Remember that SOAP is really just a
specification for how data is passed between client and server...not a
set of libraries or classes for a specific language. It specifies how
data is marshalled and unmarshalled and the form of the XML envenlope
that contains the data.
You would probably find that RMI, in general, is faster than SOAP, but
you should weigh into your equation whether the language independence is
important to you or not. If you create a service that you are making
available to the public at large, then you must decide whether you're
going to *force* them to use your Java classes so that RMI will work for
you, or will you *allow* them to choose the language they prefer and
communicate with you via SOAP. In the business world, as long as
performance is good enough, the language independence will almost always
win that battle.
Tung Mansfield wrote:
>
> What are the pros and cons of RMI versus SOAP? I am particularly
interested
> in the performance difference between the two. I am assuming the
> communication is between two systems from two different companies where
the
> communication will most likely be through HTTP. Is RMI over HTTP still
> faster than SOAP?
--
David C. Hicks
Mach Turtle Technologies, Inc. (www.machturtle.com)
dhicks@machturtle.com
770-753-8810
RE: RMI versus SOAP
Posted by Filip Hanik <fh...@pakana.com>.
Hi David,
what about IIOP and CORBA.
You can achieve language independence with a speed faster than both RMI and
SOAP.
However, as stated in the article I replied with earlier. SOAP can be very
useful since it can run on almost any protocol.
you run it on HTTP if you have firewall problems, you can run it on
SMTP/POP3 using email. very cool actually
Filip
Filip Hanik
Technical Architect
Pakana Corporation
fhanik@pakana.com
415-371 9200 ext 3529
-----Original Message-----
From: dhicks [mailto:dhicks]On Behalf Of David C. Hicks
Sent: Friday, November 17, 2000 10:55 AM
To: soap-user@xml.apache.org
Subject: Re: RMI versus SOAP
In my own mind, the primary reason for choosing SOAP over RMI is that
SOAP is a language independent protocol. With RMI, you have to assume
that you have Java on both sides. With SOAP, I can have a Java-based
client talking to a C++ server...or basically any combination of
languages that I choose. Remember that SOAP is really just a
specification for how data is passed between client and server...not a
set of libraries or classes for a specific language. It specifies how
data is marshalled and unmarshalled and the form of the XML envenlope
that contains the data.
You would probably find that RMI, in general, is faster than SOAP, but
you should weigh into your equation whether the language independence is
important to you or not. If you create a service that you are making
available to the public at large, then you must decide whether you're
going to *force* them to use your Java classes so that RMI will work for
you, or will you *allow* them to choose the language they prefer and
communicate with you via SOAP. In the business world, as long as
performance is good enough, the language independence will almost always
win that battle.
Tung Mansfield wrote:
>
> What are the pros and cons of RMI versus SOAP? I am particularly
interested
> in the performance difference between the two. I am assuming the
> communication is between two systems from two different companies where
the
> communication will most likely be through HTTP. Is RMI over HTTP still
> faster than SOAP?
--
David C. Hicks
Mach Turtle Technologies, Inc. (www.machturtle.com)
dhicks@machturtle.com
770-753-8810
Re: RMI versus SOAP
Posted by "David C. Hicks" <dh...@machturtle.com>.
In my own mind, the primary reason for choosing SOAP over RMI is that
SOAP is a language independent protocol. With RMI, you have to assume
that you have Java on both sides. With SOAP, I can have a Java-based
client talking to a C++ server...or basically any combination of
languages that I choose. Remember that SOAP is really just a
specification for how data is passed between client and server...not a
set of libraries or classes for a specific language. It specifies how
data is marshalled and unmarshalled and the form of the XML envenlope
that contains the data.
You would probably find that RMI, in general, is faster than SOAP, but
you should weigh into your equation whether the language independence is
important to you or not. If you create a service that you are making
available to the public at large, then you must decide whether you're
going to *force* them to use your Java classes so that RMI will work for
you, or will you *allow* them to choose the language they prefer and
communicate with you via SOAP. In the business world, as long as
performance is good enough, the language independence will almost always
win that battle.
Tung Mansfield wrote:
>
> What are the pros and cons of RMI versus SOAP? I am particularly interested
> in the performance difference between the two. I am assuming the
> communication is between two systems from two different companies where the
> communication will most likely be through HTTP. Is RMI over HTTP still
> faster than SOAP?
--
David C. Hicks
Mach Turtle Technologies, Inc. (www.machturtle.com)
dhicks@machturtle.com
770-753-8810
Re: RMI versus SOAP
Posted by "David C. Hicks" <dh...@machturtle.com>.
In my own mind, the primary reason for choosing SOAP over RMI is that
SOAP is a language independent protocol. With RMI, you have to assume
that you have Java on both sides. With SOAP, I can have a Java-based
client talking to a C++ server...or basically any combination of
languages that I choose. Remember that SOAP is really just a
specification for how data is passed between client and server...not a
set of libraries or classes for a specific language. It specifies how
data is marshalled and unmarshalled and the form of the XML envenlope
that contains the data.
You would probably find that RMI, in general, is faster than SOAP, but
you should weigh into your equation whether the language independence is
important to you or not. If you create a service that you are making
available to the public at large, then you must decide whether you're
going to *force* them to use your Java classes so that RMI will work for
you, or will you *allow* them to choose the language they prefer and
communicate with you via SOAP. In the business world, as long as
performance is good enough, the language independence will almost always
win that battle.
Tung Mansfield wrote:
>
> What are the pros and cons of RMI versus SOAP? I am particularly interested
> in the performance difference between the two. I am assuming the
> communication is between two systems from two different companies where the
> communication will most likely be through HTTP. Is RMI over HTTP still
> faster than SOAP?
--
David C. Hicks
Mach Turtle Technologies, Inc. (www.machturtle.com)
dhicks@machturtle.com
770-753-8810
RE: RMI versus SOAP
Posted by Filip Hanik <fh...@pakana.com>.
http://ejbinfo.com/article.pl?sid=00/10/28/0933234&mode=thread
that is a pretty good article
Filip
Filip Hanik
Technical Architect
Pakana Corporation
fhanik@pakana.com
415-371 9200 ext 3529
-----Original Message-----
From: Tung Mansfield [mailto:mansfield@orbitcommerce.com]
Sent: Friday, November 17, 2000 8:09 AM
To: soap-user@xml.apache.org
Subject: RMI versus SOAP
What are the pros and cons of RMI versus SOAP? I am particularly interested
in the performance difference between the two. I am assuming the
communication is between two systems from two different companies where the
communication will most likely be through HTTP. Is RMI over HTTP still
faster than SOAP?
RE: RMI versus SOAP
Posted by Filip Hanik <fh...@pakana.com>.
http://ejbinfo.com/article.pl?sid=00/10/28/0933234&mode=thread
that is a pretty good article
Filip
Filip Hanik
Technical Architect
Pakana Corporation
fhanik@pakana.com
415-371 9200 ext 3529
-----Original Message-----
From: Tung Mansfield [mailto:mansfield@orbitcommerce.com]
Sent: Friday, November 17, 2000 8:09 AM
To: soap-user@xml.apache.org
Subject: RMI versus SOAP
What are the pros and cons of RMI versus SOAP? I am particularly interested
in the performance difference between the two. I am assuming the
communication is between two systems from two different companies where the
communication will most likely be through HTTP. Is RMI over HTTP still
faster than SOAP?