This week's book giveaway is in the OO, Patterns, UML and Refactoring forum. We're giving away four copies of Refactoring for Software Design Smells: Managing Technical Debt and have Girish Suryanarayana, Ganesh Samarthyam & Tushar Sharma on-line! See this thread for details.
Is RMI implictly working in a Multi-thread environment. When multiple client connect to the Server remote object, are they all accessing the same instance of the remote object or different instance. I feel very unclear in this aspect though I have many tutorial abt RMI, but none is clearly explain this. Please help
Hi, As far as I'm aware there are as many distinct instances of the remote object that you create and bind to a unique name in the registry. So for instance. If you bind the same object to two different names in the registry then as far as I gather you are referencing the same object. So as you say RMI is implicitly multithreaded - clients connect and call methods on the same instance of the remote object. Therefore this object needs to be threadsafe. I hope this helps, Cheers, Steve
A method dispatched by the RMI runtime to a remote object implementation may or may not execute in a separate thread. The RMI runtime makes no guarantees with respect to mapping remote object invocations to threads. Since remote method invocation on the same remote object may execute concurrently, a remote object implementation needs to make sure its implementation is thread-safe.
I’ve looked at a lot of different solutions, and in my humble opinion Aspose is the way to go. Here’s the link: http://aspose.com
subject: RMI server...is it multi-threaded class??