Re: Serving remote clients - RMI vs HTTP

Boss wrote:
> To give good performance you need to know well the protocol you are using,
> so if your time is important for you,  probably the Best solution for
> you is
> HTTP.
> I believe that this Protocol is faster (in every place there is no java
> it's
> faster) because of the simplicity (there is no Objects).

It really depends on what type of data you have to submit and what form of data
you need to retrieve.  If there is anything that needs marshalling or
unmarshalling of data so that it can be used, then HTTP is only as good as FTP
or TCP as a simple transport, but it adds overhead to each transfer with headers
  (request and response).  So, if you are sending 10 bytes and receiving 10
bytes in response, HTTP headers will be a significant overhead.  If you are
sending 10megabytes ands receiving back 10megabytes than http headers will be of
little concern.

So, you do have to understand what you are sending and receiving and what value
HTTP or any other protocol might provide.

Gregg Wonderly

===========================================================================
To unsubscribe, send email to [email protected] and include in the body
of the message "signoff RMI-USERS".  For general help, send email to
[email protected] and include in the body of the message "help".

For a list of frequently asked RMI questions please refer to:
http://java.sun.com/j2se/1.3/docs/guide/rmi/faq.html

To view past RMI-USERS postings, please see:
http://archives.java.sun.com/archives/rmi-users.html