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.
As I read through chapter 17 "Factories and the Activation Framework" in "JAVA RMI"(O'reilly), I find the author doesn't demostrate clearly how Activation deals when multiple clients requset the same server.
As previous chapters describe, the server distinguish requests from different clients use this method: getClientHost(). And we should use a background thread to maintain and check the clients status.
So, I want to know if I still need to do so when using the Activation.
Yes, your "new name" is fine thanks for the name change!
All the Activation Framework handles is the initial creation of the server. Any further method calls will be handled the same as other RMI calls, so if you need to distinguish calls from different clients and threads to keep track of their status, the Activation Framework isn't going to change this.
The only difference the Activation Framework may throw into this is if multiple clients perform the *initial* call to the server that creates it. This is the job of the RMID daemon, though, not your server class. I'd assume that the RMID daemon would be able to handle multiple client requests to initialize your server class correctly - but once those requests get into the method calls it's up to your class.
Joined: Apr 11, 2005
Thank you, I got it
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] question about Activation Framework