Originally posted by amit ahuja:
I guess i need to explain what i have in mind.
I'm not going to have any pool of RMI objects. My RMI object will be only one.
Amit, I think we have to clarify the picture. I'm sure you may think about RMI as a logical layer over Socket connections. So when you register your object and bind it to the RMI registry it's vert similar to creating server socket. In both cases your _single_ thread is listening to the one specific port (default 1099). That means you have only one thread. But when a remote clien looks up your server and gets new instance of a remote object then a new thread is most likely started.
But just after the control enters the RMI Object (our RemoteServer), Instead of running that thread blindly (which was started by RMI runtime) , I propose to have Pool of working Threads. and now all requests to RMI Object will be run by Threads in pool only. If all threads are busy, the requests will wait on my pool.
I dindn't fully get your idea. Your pool is supposed to contain wich objects? Instances of RemoteServer? (sounds strange, probably I'm wrong)
Believe me i'm very flexible at accepting other's view and reasoning .. just kidding
I believe:-) explain me your idea pls.
[ January 09, 2002: Message edited by: amit ahuja ][/QB]