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:
“I believe in Michael Angelo, Velasquez, and Rembrandt; in the might of design, the mystery of color, the redemption of all things by Beauty everlasting, and the message of Art that has made these hands blessed.”
—George Bernard Shaw (1856–1950)
“It’s a particular Observation I have always made, That of all Mortals, a Critick is the silliest; for by inuring himself to examine all Things, whether they are of Consequence or not, he never looks upon any Thing but with a Design of passing Sentence upon it; by which Means, he is never a Companion, but always a Censor.”
—Richard Steele (1672–1729)