ddsf:public:guidebook:06_append:glossary:r:rpc
Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision | ||
|
ddsf:public:guidebook:06_append:glossary:r:rpc [2020/10/01 12:04] murphy |
ddsf:public:guidebook:06_append:glossary:r:rpc [2021/07/14 16:33] (current) murphy ↷ Links adapted because of a move operation |
||
|---|---|---|---|
| Line 1: | Line 1: | ||
| ===== Remote Procedure Call (RPC) ===== | ===== Remote Procedure Call (RPC) ===== | ||
| - | [[ddsf:private:cookbook:06_append:glossary| Return to Glossary ]] | + | [[ddsf:public:guidebook:06_append:glossary:start| Return to Glossary ]] |
| - | **Remote Procedure Call (RPC)** are used in distributed computing. It 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. This is a form of [[ddsf:private:cookbook:06_append:glossary:c:client-server|client–server]] interaction (caller is client, executor is [[ddsf:private:cookbook:06_append:glossary:s:server|server]]), typically implemented via a request–response message-passing system. In the object-oriented programming paradigm, RPCs are represented by remote method invocation (RMI) in Java. The RPC model implies a level of location transparency, namely that calling procedures are largely the same whether they are 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. | + | **Remote Procedure Call (RPC)** are used in distributed computing. It 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. This is a form of [[ddsf:public:guidebook:06_append:glossary:c:client-server|client–server]] interaction (caller is client, executor is [[ddsf:public:guidebook:06_append:glossary:s:server|server]]), typically implemented via a request–response message-passing system. In the object-oriented programming paradigm, RPCs are represented by remote method invocation (RMI) in Java. The RPC model implies a level of location transparency, namely that calling procedures are largely the same whether they are 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. |
| Source: [[https://en.wikipedia.org/wiki/Remote_procedure_call | Remote Procedure Call (RPC) ]] | Source: [[https://en.wikipedia.org/wiki/Remote_procedure_call | Remote Procedure Call (RPC) ]] | ||
ddsf/public/guidebook/06_append/glossary/r/rpc.1601568291.txt.gz · Last modified: 2020/10/01 12:04 by murphy
