There seems to be a couple of issues with your example.
I assume Thread.wait() is actually this.wait(), since there is no such method on Thread. And the wait should be called on the same object as is used to do the synchronization.
Assuming this, when Client 1 calls the lock.wait(), the monitor on the synchronization block is released. This means that Client 2 can access the method and will eventually block at the same wait method. The wait() will release when some other thread calls a notify() on the same instance of MyServer.
As for serialization, that occurs before this method is called. It would have occurred within the RMI code which calls this method.
发布评论
评论（2）
您的示例似乎存在一些问题。
我假设 Thread.wait() 实际上是 this.wait()，因为 Thread 上没有这样的方法。 并且应该在用于执行同步的同一对象上调用等待。
假设这样，当客户端1调用lock.wait()时，同步块上的监视器被释放。 这意味着客户端 2 可以访问该方法，并最终会阻塞在同一个等待方法上。 当其他线程在同一 MyServer 实例上调用 notification() 时，wait() 将释放。
至于序列化，发生在调用该方法之前。 它可能发生在调用此方法的 RMI 代码中。
There seems to be a couple of issues with your example.
I assume Thread.wait() is actually this.wait(), since there is no such method on Thread. And the wait should be called on the same object as is used to do the synchronization.
Assuming this, when Client 1 calls the lock.wait(), the monitor on the synchronization block is released. This means that Client 2 can access the method and will eventually block at the same wait method. The wait() will release when some other thread calls a notify() on the same instance of MyServer.
As for serialization, that occurs before this method is called. It would have occurred within the RMI code which calls this method.
bar 参数在与调用 foo 方法的请求相同的请求中传输，该请求是 RMI 协议。
The bar parameter is transmitted in the same request as the request to invoke the foo method, which is part of the RMI protocol.