https://github.com/29dch/custom-rpc-framework
自定义RPC框架
https://github.com/29dch/custom-rpc-framework
rpc rpc-framework
Last synced: about 1 year ago
JSON representation
自定义RPC框架
- Host: GitHub
- URL: https://github.com/29dch/custom-rpc-framework
- Owner: 29DCH
- Created: 2019-02-26T11:47:16.000Z (about 7 years ago)
- Default Branch: master
- Last Pushed: 2019-02-26T13:36:31.000Z (about 7 years ago)
- Last Synced: 2025-01-10T10:54:01.437Z (about 1 year ago)
- Topics: rpc, rpc-framework
- Language: Java
- Homepage:
- Size: 27.3 KB
- Stars: 0
- Watchers: 2
- Forks: 0
- Open Issues: 0
-
Metadata Files:
- Readme: README.md
Awesome Lists containing this project
README
# Custom-RPC-Framework
RPC:Remote Procedure Call
Remote Procedure Call (RPC) is a protocol that one program can use to request a service from a program located in another computer on a network without having to understand the network's details. A procedure call is also sometimes known as a function call or a subroutine call. RPC uses the client-server model.
In distributed computing, a remote procedure call (RPC) is when a computer program causes a procedure (subroutine) to execute in a different address space (commonly on another computer on a shared network), which is coded as if it were a normal (local) procedure call, without the programmer explicitly coding the details for the remote interaction. That is, the programmer writes essentially the same code whether the subroutine is local to the executing program, or remote.[1] This is a form of client–server interaction (caller is client, executor is server), typically implemented via a request–response message-passing system. In the object-oriented programming paradigm, RPC calls are represented by remote method invocation (RMI). The RPC model implies a level of location transparency, namely that calling procedures is largely the same whether it is local or remote, but usually they are not identical, so local calls can be distinguished from remote calls. Remote calls are usually orders of magnitude slower and less reliable than local calls, so distinguishing them is important.
RPCs are a form of inter-process communication (IPC), in that different processes have different address spaces: if on the same host machine, they have distinct virtual address spaces, even though the physical address space is the same; while if they are on different hosts, the physical address space is different. Many different (often incompatible) technologies have been used to implement the concept.