Implementing Remote procedure calls

Abstract

Remote procedure calls (RPC) appear to be a useful paradig m for providing communication across a network between programs written in a high-level language. This paper describes a package providing a remote procedure call facility, the options that face the designer of such a package, and the decisions ~we made. We describe the overall structure of our RPC mechanism, our facilities for binding RPC clients, the transport level communication protocol, and some performance measurements. We include descriptioro~ of some optimizations used to achieve high performance and to minimize the load on server machines that have many clients.

Propagation of program control: A tool for distributed disease surveillance

“…Propagation of program control allows program control to be moved between hosts, in the same manner as mobile code, by transferring a task specification and data between the hosts. The principle is located somewhere between process migration and remote procedure call [52]. Instead of letting a process or software agent wander autonomously at its own will between hosts, we ensure that the software agent is under the control of several authorities at all times.…”

Visual Supercomputing: Technologies, Applications and Challenges

“…Distributed memory architectures typically involve static interconnection networks, which may be of a variety connection topologies [28]. In such architectures, some kind of mechanism for message passing [29] or remote procedure calls (RPC) [30] is required. The former enables data communication between remote processes, and the latter facilitates server-client communication by allowing a client to activate pre-defined remote procedures at a server and exchange data in a manner similar to conventional subroutine calls.…”

Design of a Remote Procedure Call system for object-oriented distributed programming

“…21. In most of the these RPC systems the design goals, in general, have been reliability, 3,4,20,22 , performance, 2,21,23,24 and support for heterogeneous systems. 19 A critique of the RPC paradigm is presented in Ref.…”

“…The concept of network transparency 1 plays a central role in addressing many of these challenges; its purpose is to provide simple mechanisms for distributed computing by hiding from the programmer the complexities of the underlying network architecture. Due to its simple abstractions and its support for network transparency, the paradigm of the Remote Procedure Call (RPC) 2,3,4 has become widely popular in commercial systems 5,6,7 for building distributed software. It is based on the client-server model of computing.…”