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 places which I have described may seem strange and remote to my townsmen ... our account may have made no impression on your minds. But what is our account? In it there is no roar, no beach-birds, no tow-cloth.”
—Henry David Thoreau (1817–1862)
“O curse of marriage,
That we can call these delicate creatures ours
And not their appetites! I had rather be a toad,
And live upon the vapour of a dungeon
Than keep a corner in the thing I love
For others’ uses.”
—William Shakespeare (1564–1616)