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:
“It’s important for parents to watch for trouble and convey to their daughters that, if it comes, they are strong enough to deal with it. Parents who send their [adolescent] daughters the message that they’ll be overwhelmed by problems aren’t likely to hear what’s really happening.”
—Mary Pipher (20th century)
“The statue is then beautiful when it begins to be incomprehensible, when it is passing out of criticism, and can no longer be defined by compass and measuring-wand, but demands an active imagination to go with it, and to say what it is in the act of doing.”
—Ralph Waldo Emerson (1803–1882)