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 thief. Once committed beyond a certain point he should not worry himself too much about not being a thief any more. Thieving is God’s message to him. Let him try and be a good thief.”
—Samuel Butler (1835–1902)
“The business eternally passing thro’ my mind and occupying it exclusively, wipes out at once the recollection of things which have been presented to it but once, and on which it has had no occasion to recur.”
—Thomas Jefferson (1743–1826)