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:
“Christina Bailey: I was just thinking how much you can tell about a person from such simple things. Your car, for instance.
Mike Hammer: Now what kind of message does it send you?
Christina: You have only one real, lasting love.
Mike: Now who could that be?
Christina: You. You’re one of those self-indulgent males who thinks about nothing but his clothes, his car, himself. I’ll bet you do push-ups every morning just to keep your belly hard.”
—A.I. (Albert Isaac)
“Is it not passing brave to be a King,
And ride in triumph through Persepolis?”
—Christopher Marlowe (1564–1593)