Xerox Corp. Courier: The Remote Procedure Call Protocol. Technical Report XNSS 038112, Xerox Corp, Dec 1981.  Home/Search   Document Not in Database   Summary   Related Articles   Check

....[32] have used (machine specic) diffs to propagate updates, but only on homogeneous platforms. Several projects, including ShareHolder citeshareholder, Globus [15] and WebOS [34] use URL like names for distributed objects or les. Interface description languages date from Xerox Courier [37] and related systems of the early 1980s. Precedents for the automatic management of pointers include Herlihy s thesis work [17] LOOM [18] and the more recent pickling (serialization) of Java [29] Smart RPC [19] is an extension to conventional RPC that allows argument passing using callby ....

Xerox Corporation. Courier: The Remote Procedure Call Protocol. Technical Report XSIS 038112, Dec. 1981.

....and caching of remote data during individual remote invocations, but with a restricted type system, and with no provision for coherence across calls. RPC systems have long supported automatic deep copy transmission of structured data among heterogeneous languages and machine architectures [12, 25], and modern standards such as XML provide a language independent notation for structured data. To the best of our knowledge, however, no one to date has automated the typesafe sharing of structured data in its internal (in memory) form across multiple languages and platforms, or optimized that ....

Xerox Corporation. Courier: The Remote Procedure Call Protocol. Technical Report XSIS 038112, Dec. 1981.

....[32] have used (machine specific) diffs to propagate updates, but only on homogeneous platforms. Several projects, including ShareHolder citeshareholder, Globus [15] and WebOS [34] use URL like names for distributed objects or files. Interface description languages date from Xerox Courier [37] and related systems of the early 1980s. Precedents for the automatic management of pointers include Herlihy s thesis work [17] LOOM [18] and the more recent pickling (serialization) of Java [29] Smart RPC [19] is an extension to conventional RPC that allows argument passing using callby ....

Xerox Corporation. Courier: The Remote Procedure Call Protocol. Technical Report XSIS 038112, Dec. 1981.

....mechanism to establish consistency and support distributed replication of objects for reliability in the presence of mobility and weak connectivity. Various Linda systems [31, 36] also provide a non object oriented distributed shared store. Interface description languages date from Xerox Courier [47] and related systems of the early 1980s. Precedents for the automatic management of pointersinclude Herlihy s thesis work [18] LOOM [22] and the more recent pickling (serialization) of Java [33] Friedman [15] and Agrawal et al. 1] have shown how to combine certain pairs of consistency models ....

Xerox Corporation. Courier: The Remote Procedure Call Protocol. Technical Report XSIS 038112, Dec. 1981. 26

....declares interfaces and data to be used for remote interoperation in a specialized language with its own type system. An IDL compiler translates these declarations into equivalent declarations in each PL and also generates the marshaling stubs. IDLbased tools include research results like Courier [17] and Matchmaker [9] as well as the competing proposals of various companies and consortia, such as SUN ONC [15] OSF DCE [13] Microsoft s Distributed COM [11] and OMG s CORBA [12] Because the IDL s type system has some translation into each language, multi language interoperation is achieved. ....

The Xerox Corporation. Courier: The Remote Procedure Call Protocol, December 1981. Technical Report XSIS 038112. 15

....types to be used throughout a project, both for computation and for intercomponent communication, at the expense of limiting a project to a single language. This limitation can be unacceptable when integrating information systems that are already implemented in multiple languages. IDL compilers [13, 15, 17, 18, 19, 22, 24] support multiple languages by generating stubs from IDL. However, IDL compilers also generate programming language data declarations from the IDL that must be used for intercomponent communication. These imposed types are rarely what the programmer would have chosen for computational purposes. ....

The Xerox Corporation. Courier: The Remote Procedure Call Protocol, December 1981. Technical Report XSIS 038112.

....oriented toward highperformance parallel execution. Early work appears to have focussed primarily on load balancing and process management. Various Linda systems [32, 37] also provide a nonobject oriented distributed shared store. Interface description languages date from Xerox Courier [47] and related systems of the early 1980s. Precedents for the automatic management of pointers include Herlihy s thesis work [19] LOOM [24] and the more recent pickling (serialization) of Java [34] Friedman [15] and Agrawal et al. 2] have shown how to combine certain pairs of consistency ....

Xerox Corporation. Courier: The Remote Procedure Call Protocol. Technical Report XSIS 038112, Dec. 1981.

....support for distributed shared state to be uniquely general and transparent, much of the underlying technology is borrowed from previous work of others. RPC and message passing systems have used interface description languages to accommodate heterogeneous machine types for at least 20 years [15]. Popular modern systems include Sun s XDR [13] Microsoft s DCOM [10] and various flavors of CORBA [7] Herlihy s thesis work [4] pioneered deep copy semantics for linked data structures. Similar facilities can be found in DCOM, in Emerald [5] and in the more recent pickling (serialization) ....

Xerox Corporation. Courier: The Remote Procedure Call Protocol. Technical Report XSIS 038112, DEC 1981.

....file, which is then lexically included in various compilations as he goes about implementing components. The parts of C that are used to declare types and functions thus constitute an IDS. In this paper, we consider one very common motivation for using an IDL: to support distributed computing [13, 12, 16, 11, 17, 7, 6], where the IDL s role is to specify message or function signatures for remote communication. These languages do not go much beyond typical programming language IDSs in supporting specification: their primary purpose is to serve as additional source languages for the part of the implementation ....

The Xerox Corporation. Courier: The Remote Procedure Call Protocol, December 1981. Technical Report XSIS 038112. 12

....running applications, thus enabling cooperative computing over a network [22] The performance of the current prototype is comparable to that of Sun RPC. Parsons [27] has compared the usability and performance of Concert C with other tools for distributed programming including Isis [10] and PVM [32]. We are adding full interoperability with OSF DCE, are currently designing Concert C , and are investigating preliminary designs for Concert Fortran. We are interested in developing tools for process management and control, such as a distributed visualizer debugger, and utilities which aid in ....

The Xerox Corporation. Courier: The Remote Procedure Call Protocol, December 1981. Technical Report XSIS 038112.

....oriented toward highperformance parallel execution. Early work appears to have focussed primarily on load balancing and process management. Various Linda systems [37, 32] also provide a nonobject oriented distributed shared store. Interface description languages date from Xerox Courier [46] and related systems of the early 1980s. Precedents for the automatic management of pointers include Herlihy s thesis work [19] LOOM [24] and the more recent pickling (serialization) of Java [34] Friedman [15] and Agrawal et al. 2] have shown how to combine certain pairs of consistency ....

Xerox Corporation. Courier: The Remote Procedure Call Protocol. Technical Report XSIS 038112, DEC 1981.

....data types (i.e. UTCTime) are represented as strings and, probably, should not. 3.5.2 Specific problems of XDR XDR was designed for simple and efficient applications in mind, usually implementable as remote procedure calls on top of datagrams. It is mainly an extension of Xerox Courier syntax [15], adapted to newer 32 bit machines and the syntax of C. The basic types and structures are defined after their encodings, so the definition of new encodings means the invention of new type names (for example, there is an hyper integer for a 64 bit integer; from the standard is suggested the ....

Xerox Corporation. Courier: The remote procedure call protocol. Xerox OPD, 3333 Coyote Hill Rd, Palo Alto, Ca 94304, (XSIS 038112), December 1981. 53

....Size Name Size Opt Block Name Opt Block Name cont d Figure 2: Description of the control structure for blocks. borrowed from previous work of others. RPC and message passing systems have used interface description languages to accommodate heterogeneous machine types for at least 20 years [14]. Popular modern systems include Sun s XDR [12] Microsoft s DCOM [9] and various flavors of CORBA [6] Herlihy s thesis work [3] pioneered deep copy semantics for linked data structures. Similar facilities can be found in DCOM, in Emerald [4] and in the more recent pickling (serialization) ....

Xerox Corporation. Courier: The Remote Procedure Call Protocol. Technical Report XSIS 038112, Dec. 1981. 6

....oriented toward high performance parallel execution. Early work appears to have focussed primarily on load balancing and process management. Various Linda systems [32, 29] also provide a non objectoriented distributed shared store. Interface description languages date from Xerox Courier [40] and related systems of the early 1980s. Precedents for the automatic management of pointers include Herlihy s thesis work [16] LOOM [21] and the more recent pickling (serialization) of Java [30] Friedman [12] and Agrawal et al. 2] have shown how to combine certain pairs of consistency ....

Xerox Corporation. Courier: The Remote Procedure Call Protocol. Technical Report XSIS 038112, Dec. 1981.

....virtual windtunnel is Distributed Library (dlib) 3] The workstation acts as a client and the supercomputer acts as the server. Like many systems which provide for distributed processing, dlib is a high level interface to network services based on the remote procedure call (RPC) model [7] 8] 9][10]. However, unlike most of these systems, dlib was developed to provide a service which allows for a conversation of arbitrary length within a single context between client and server. The dlib server process is designed to be capable of storing state information which persists from call to call, ....

Xerox Corporation. Courier: the remote procedure call protocol. Xerox System Integration Standard (XSIS) 038112, (Dec. 1981). 14

....and summarize some general lessons distilled from our experience. 2 Related work This paper mainly concerns two research areas, the specification of message formats for communication among processes and the use of domain specific languages for software engineering. 2. 1 Message formats Courier [1], part of the Xerox Network Systems (XNS) architecture of the 1970s, was one of the first languages designed to specify a machine independent encoding of data structures as well as tools to produce those encodings from machine specific data representations. Several data encoding standards have ....

Xerox Corporation. Courier: the remote procedure call protocol. Technical Report XSIS 038112, December 1981.

....do dynamic type checking at run time. This would mean, that the implementation of a remote method Implementation Aspects 91 would have to check the class of each argument before any processing is done [63] Related Work Many RPC systems have been built for use in UNIX systems. Courier RPC [153] developed at Xerox, the Cedar RPC system [22] and Sun RPC [140] are just a few examples. Some of them, like Cedar RPC, were designed to work with a single language. There exist others which can work in a multi language, multimachine environment. Coulouris [47] provides a general discussion of ....

Xerox Corporation. Courier: The Remote Procedure Call Protocol. Stamford, Connecticut, 1981. Xerox Integration Standard XSIS-038112.

....synchronization semantics at the client similar to normal procedure call. Numerous examples of different RPC services and implementations exist, including Firefly RPC [19] Alphorn [3] lightweight RPC [4] and Peregrine [14] Among the commercial RPC packages released have been Courier from Xerox [24], Sun RPC [22] Netwise RPC from Novell Netware, and NCA from Apollo [2] On the surface, the semantics of RPC seem very simple, yet the reality is that there are subtleties and variations. For example, there are many ways to define how an RPC service deals with server and communication failures. ....

Xerox. Courier: The remote procedure call protocol. Technical Report XSIS 038112, Xerox System Integration Standard, Stamford, CT, Dec 1981.

....the other machine. Including these encoding and decoding operations in the stubs of both sites makes it possible to preserve the data types in a heterogeneous environment. The practicality of this approach is well recognized, and used as the basis for many experimental [3, 2, 9, 8] and commercial [6, 7, 17, 18] distributed systems. However, conventional RPC systems have a crucial restriction: only certain data types can be used as the arguments of a remote procedure. For example, pointers or higher order functions cannot be used directly as arguments. In ordinary programming languages, it is common for ....

XEROX Corporation. Courier: the Remote Procedure Call Protocol, Dec. 1981. XEROX system integration standard XSIS-038112.

....similar to normal procedure call. Numerous examples of different RPC services and implementations exist, including Firefly RPC [SB90] Alphorn [AGH 91] lightweight RPC [BALL90] Peregrine [JZ93] and SUPRA RPC [Sto94] Among the commercial RPC packages released have been Courier from Xerox [Xer81] Sun RPC [Sun88] Netwise RPC from Novell Netware, NCA from Apollo [Apo89] and DCE RPC. On the surface, the semantics of RPC seem very simple, yet the reality is that there are subtleties and variations. For example, there are many ways to define how an RPC service deals with server and ....

Xerox. Courier: The remote procedure call protocol. Technical Report XSIS 038112, Xerox System Integration Standard, Stamford, CT, Dec 1981.

....cooperative systems are one of the target applications of contemporary standardizations such as OSF DCE [33] OMG CORBA [31] and DCOM [10] 1. 1 Remote Procedure Call and Distributed Shared Memory Two technologies for distributed programming have been widely used: the remote procedure call (RPC) [40, 5, 4, 16, 19, 14, 2, 36] and distributed shared memory (DSM) 28, 37, 30] There are three distinctive differences between these technologies [11] One is that the RPC inherently provides the data passing semantics, whereas DSM provides the data sharing semantics. The second is that the RPC provides distribution ....

....virtual memory management, 2) coherency protocols, and (3) RPC based stub generation (i.e. language preprocessing) Generally, a reference across an address space boundary is meaningless unless dereference operations are executed at the address space where it is created. Conventional RPC systems [40, 5] and object oriented distributed systems [22, 34, 6, 18, 21, 8] callbacks the target address space every time a remote reference is dereferenced. The VM integrated RPC automatically detects the first dereference of a remote reference by using a memory management unit (MMU) which is equipped with ....

XEROX Corporation. Courier: the Remote Procedure Call Protocol, Dec. 1981. XEROX system integration standard XSIS-038112.

....these factors make this work and our work with Schooner complementary rather than competitive. The third category includes systems that are related to Schooner s RPC mechanism. These other RPC schemes have features such as external data representations, specification languages, and stub compilers [4, 7, 28, 33]. Several of these systems also emphasize heterogeneity, including Matchmaker [22] Horus [14] HRPC [6] and Cicero Nestor [21] The primary distinction between this work and Schooner is again one of orientation: the main aim of these systems is to support interprocess communication for ....

Xerox Corp. Courier: The Remote Procedure Call Protocol. Xerox System Integration Standard XSIS 038112, Xerox Corp., Stamford CT, December 1981.

....by its type in an operation called marshalling. On receipt, the complementary unmarshalling operation converts the value from its standard representation into an appropriate local one. A number of widely used standard representations exist, each defining a set of transmissible data types [Xerox 1981; ANSA 1986; Dean et al. 1987; Zahn et al. 1990; Sun 1992] Marshalling is a recursive process. Complex types such as structures and arrays are built on top of primitive ones such as integers and reals. Marshalling progressively decomposes a value until it terminates with conversion of its ....

Xerox, December 1981. Courier: The Remote Procedure Call Protocol. Xerox Corporation. Xerox System Integration Standard 038112.

No context found.

Xerox Corp. Courier: The Remote Procedure Call Protocol. Technical Report XNSS 038112, Xerox Corp, Dec 1981.

No context found.

Xerox Corporation. Courier: The Remote Procedure Call Protocol. Technical Report XSIS 038112, Dec. 1981.

First 50 documents

Online articles have much greater impact   More about CiteSeer.IST   Add search form to your site   Submit documents   Feedback  

CiteSeer.IST - Copyright Penn State and NEC