RPC understanding

My understanding is that ：

The principle of server communication is a socket The server A, another socket client B, Now if you want to communicate, write or read directly in stream mode . This will allow communication , But there's a problem . How to know more ？ For example, you need to send the stream size , code ,Ip etc. . So there's an agreement , Agreements are norms , That is, the sent stream carries a lot of content . So back to the question .

The content sent is the text type , The client has to be serialized , Then the commonly used ones are json,xml And so on

If you want to make the content smaller , So there's binary . Turn text into binary and pass it on .

Speaking of rpc And http Interface , Don't be too complicated .rpc The protocol is simpler, the content is smaller , So the efficiency is a little higher

then rpc What is it? . Namely socket Add dynamic proxy , Think about it , Why can the client call your service .

rpc The communication principle is the interface class to be called , Method parameters , Send it to the server , After the server finishes processing , Return the result to us .

Go and have a look http://javatar.iteye.com/blog/1123915, I hope it helps you