Programmers Stack Exchange is a question and answer site for professional programmers interested in conceptual questions about software development. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

Question: Why might RMI be a sensible option for communication between client and server in a web application?

So why would RMI be used for communication between client and server in web apps?

share|improve this question
What do you mean by sensible option? – Abimaran Kugathasan Jan 7 '11 at 16:00
The format of the question suggests this may come from a book, and is probably quite outdated. My best guess would be that it's referring to the client being a Java applet, which was sort-of in fashion in the late 90s. In that context, it would make a lot more sense than it does now. – Daniel B Oct 1 '12 at 8:23

It's not.

RMI is a binary protocol for serializing and sending Java objects between two end-points and you really need those end-points to be JVM's for that to work.

With "web applications" I assume you mean html+http+javascript which would be incredible hard (if at all possible) to use with RMI.

share|improve this answer
And the end-points need to be compatible JVM's even. – user1249 Jan 8 '11 at 18:29
and the end points also need compatible code (or enough security clearance to download&execute code) – ratchet freak Apr 4 '12 at 7:54

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.