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:
“Oh! what a poor thing is human life in its best enjoyments!—subjected to imaginary evils when it has no real ones to disturb it! and that can be made as effectually unhappy by its apprehensions of remote contingencies as if it was struggling with the pains of a present distress!”
—Samuel Richardson (1689–1761)
“Mahomet made the people believe that he would call a hill to him, and from the top of it offer up his prayers for the observers of the Law. The people assembled; Mahomet called the hill to come to him again and again; and when the hill stood still, he was never a whit abashed, but said, If the hill will not come to Mahomet, Mahomet will go to the hill.”
—Francis Bacon (1561–1626)