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:
“All our civilization had meant nothing. The same culture that had nurtured the kindly enlightened people among whom I had been brought up, carried around with it war. Why should I not have known this? I did know it, but I did not believe it. I believed it as we believe we are going to die. Something that is to happen in some remote time.”
—Mary Heaton Vorse (1874–1966)
“... the Department of Justice is committed to asking one central question of everything we do: What is the right thing to do? Now that can produce debate, and I want it to be spirited debate. I want the lawyers of America to be able to call me and tell me: Janet, have you lost your mind?”
—Janet Wood Reno (b. 1938)