Well, let's take a look at the specific implementation of RPC's underlying server class, many design ideas and practical ways to value learning. The focus is not to read the source code, but to learn from the source of what.
In particular, the use of wait and notify is a good example of learning and, of course, reflection ...
The Server start () method is the Ingress class, and the basic thread is the daemon way
Let's take a look at what the run has done, primarily to establish a socket read client request.
And the customer requests and encapsulates the call into the queue to remind consumers to use.
Here is the handler, mainly processing, connection accepted objects
The specific invocation method depends on the implementation class, example Namenode code.
?
This completes the entire server code block.
The RPC server source code analysis for Hadoop