In computer science, a remote procedure call (RPC) is an inter-process communication that allows a computer program to cause a subroutine or procedure to execute in another address space (commonly on another computer on a shared network) without the programmer explicitly coding the details for this remote interaction. That is, the programmer writes essentially the same code whether the subroutine is local to the executing program, or remote. When the software in question uses object-oriented principles, RPC is called remote invocation or remote method invocation.
Many different (often incompatible) technologies can be used to implement the concept.
| Internet protocols |
|---|
| Application layer |
|
| Transport layer |
|
| Routing protocols * |
|
| Internet layer |
|
| Link layer |
|
| * Not a layer. A routing protocol belongs either to application or network layer. |
Read more about Remote Procedure Call: History and Origins, Message Passing, Other RPC Analogues
Famous quotes containing the words remote and/or call:
“The Americans never use the word peasant, because they have no idea of the class which that term denotes; the ignorance of more remote ages, the simplicity of rural life, and the rusticity of the villager have not been preserved among them; and they are alike unacquainted with the virtues, the vices, the coarse habits, and the simple graces of an early stage of civilization.”
—Alexis de Tocqueville (1805–1859)
“The principles of the good society call for a concern with an order of being—which cannot be proved existentially to the sense organs—where it matters supremely that the human person is inviolable, that reason shall regulate the will, that truth shall prevail over error.”
—Walter Lippmann (1889–1974)