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:
“The whole idea of image is so confused. On the one hand, Madison Avenue is worried about the image of the players in a tennis tour. On the other hand, sports events are often sponsored by the makers of junk food, beer, and cigarettes. What’s the message when an athlete who works at keeping her body fit is sponsored by a sugar-filled snack that does more harm than good?”
—Martina Navratilova (b. 1956)
“On a day—alack the day—
Love, whose month is ever May,
Spied a blossom passing fair
Playing in the wanton air.”
—William Shakespeare (1564–1616)