Tuesday, September 12, 2006 02:59 AM
I have a question regarding spawning threads inside a class that extends UnicastRemoteObject. Would it be okay to spawn new thread(s) in the constructor/ remote methods of the class that extends UnicastRemoteObject? Are there any pitfalls to doing so? Is it against the suggested practice of writing RMI server code since the RMI server runtime is unware of the threads that are spawned and hence cannot be efficiently managed by it?