Message Passing
An RPC is initiated by the client, which sends a request message to a known remote server to execute a specified procedure with supplied parameters. The remote server sends a response to the client, and the application continues its process. While the server is processing the call, the client is blocked (it waits until the server has finished processing before resuming execution), unless the client sends an asynchronous request to the server, such as an XHTTP call. There are many variations and subtleties in various implementations, resulting in a variety of different (incompatible) RPC protocols.
An important difference between remote procedure calls and local calls is that remote calls can fail because of unpredictable network problems. Also, callers generally must deal with such failures without knowing whether the remote procedure was actually invoked. Idempotent procedures (those that have no additional effects if called more than once) are easily handled, but enough difficulties remain that code to call remote procedures is often confined to carefully written low-level subsystems.
Read more about this topic: Remote Procedure Call
Famous quotes containing the words message and/or passing:
“If you have a message you want to send to hell, give it to me; I’ll carry it!”
—Administration in the State of Sout, U.S. public relief program (1935-1943)
“It may be possible to do without dancing entirely. Instances have been known of young people passing many, many months successively, without being at any ball of any description, and no material injury accrue either to body or mind; Mbut when a beginning is made—when felicities of rapid motion have once been, though slightly, felt—it must be a very heavy set that does not ask for more.”
—Jane Austen (1775–1817)