Confusion with RMI internal working

Hi,

I am a little confused with internal working of the RMI system.

Say my client has obtained a reference to the remote server object via lookup.

Now the client can make an RMI call on the server to register itself for callback purposes.

Now before the client could make this call, the server goes into loop checking whether the reference to client has been set or not.

Since the server goes into loop, the thread is occupied in the loop.

Now the client makes a RMI call to set the reference to itself in the server for callback purposes.

I thought that this should not work as the server thread is busy in the loop. But to my surprise the reference is set properly and the server thread comes out of loop.. Any ideas why this is happening..

Does the RMI call makes a seperate thread of execution.

Any replies on this working would be helpful.

Thanks

Vipul

[931 byte] By [vipul.guptaa] at [2007-10-2 19:37:48]
# 1
> Does the RMI call makes a seperate thread of execution.Yes.
ejpa at 2007-7-13 21:26:20 > top of Java-index,Core,Core APIs...