wood burning stoves 2.0*
The moose likes Distributed Java and the fly likes Is RMI adequate? Big Moose Saloon
  Search | Java FAQ | Recent Topics | Flagged Topics | Hot Topics | Zero Replies
Register / Login


Win a copy of Murach's Java Servlets and JSP this week in the Servlets forum!
JavaRanch » Java Forums » Java » Distributed Java
Bookmark "Is RMI adequate?" Watch "Is RMI adequate?" New topic
Author

Is RMI adequate?

Mattias Johansson
Greenhorn

Joined: Oct 21, 2007
Posts: 11
I'm going to create a networked application that is going to support 1000+ users and I'm wondering if RMI is adequate for this situation. I was thinking about it at first but then I read something about the threading on the RMI server side that it can create a lot of them. If RMI is not suitable for this kind of application which networking technology should I use? What is the advantage with this technology over RMI in this situation?

Thanks in advance
Mattias
Vassili Vladimir
Ranch Hand

Joined: Mar 08, 2007
Posts: 1585
Hi,

As far as i know, Sockets give you a complete control over threads.

Best of luck ...


Vassili ...
SCJP 5.0, SCWCD 1.4, SCJA 1.0
Mattias Johansson
Greenhorn

Joined: Oct 21, 2007
Posts: 11
Ok, but in what way will sockets help me to perform better in this kind of application?
I read somewhere that when sending small amounts of data sockets wasn't a good option because of starting a new socket connection, send the data and then close the connection make a big overhead. Is it better to keep the socket open? But won't that affect the server if there is a lot of users connected to it?
[ October 24, 2007: Message edited by: Mattias Johansson ]
Vassili Vladimir
Ranch Hand

Joined: Mar 08, 2007
Posts: 1585
Hi,

Multi-Threading is the way to go then!

Best of luck ...
Mattias Johansson
Greenhorn

Joined: Oct 21, 2007
Posts: 11
Ok, but in what way should I use multi-threading? Connecting by sockets and then create a new thread per connected client? Or use RMI where threads are created automatically when you connect to the RMI server?
Is it preferred to use a thread pool together with sockets or might that slow down the performance if the clients have to wait for a long time before their requests are dealt with?
Does anyone have any good websites that talk about this topic?
 
I agree. Here's the link: http://aspose.com/file-tools
 
subject: Is RMI adequate?
 
Similar Threads
JAX -RPC
Questin on listeners
altering DBAccess interface
Question about JNI and RMI-IIOP
Revision help