K. G. Hamilton, A Remote Procedure Call System, Ph.D. Thesis, Technical Report No. 70, Computer Laboratory, University of Cambridge, December 1984.  Home/Search   Document Not in Database   Summary   Related Articles   Check

....transmission, the remote procedure call provides marshalling of the parameters for message transmission, i.e. the list of parameters is collected together by the system to form a message. A remote procedure call mechanism should exhibit the following six properties [Nelson 1981] LeBlanc 1982] [Hamilton 1984] and [Goscinski 1991] A transparent remote procedure call implementation must maintain the same semantics as that used for local procedure calls. Client program read( Client computer parameters Pack send( receive( Unpack parameters receive( Unpack Pack parameters send( ....

K. G. Hamilton, A Remote Procedure Call System, Ph.D. Thesis, Technical Report No. 70, Computer Laboratory, University of Cambridge, December 1984.

....outages, and practical engineering issues such as debugging across multiple processes on distributed computers. One of the primary challenges to create a distributed application is the need to partition and place pieces of the application. Although successive generations of middleware (such as RPC [4, 15, 34], CORBA [35, 42] and DCOM [8] have brought the advantages of service location transparency, dynamic object instantiation, and object oriented programming to distributed applications, the process of distributed application decomposition has changed little: programmers manually divide applications ....

Hamilton, K. G. A Remote Procedure Call System. Ph. D. Dissertation, Computer Laboratory TR 70. University of Cambridge, Cambridge, UK, 1984.

....makes stores more autonomous because each has now a local copy of the object and does not depend on the network or the other store to access its value. 4. 1 Examples Most RPC systems pass parameters by copy, including the first RPC mechanism implemented by Birrel and Nelson [4] Hamilton s RPC [10], Argus [19] the RPC product from Sun [29] and OSF [27] XEROX s ILU [13] and our RPC described below. Napier88 RPC [24] is a type safe RPC mechanism for Napier88. Based on Sun RPC [29] Napier88 RPC supports only a restricted number of type constructors as arguments to remote procedures, and ....

K. Hamilton. A Remote Procedure Call System. PhD thesis, University of Cambridge Computer Laboratory, 1984.

....support for memory management and communication between processes on the same machine, but that support for applications that run on multiple machines is weak. The current IPC mechanisms, with Remote Procedure Call as the most popular one, are adequate only for the simpler distributed applications [7, 8, 9]. The new ISIS system has several well defined layers. This paper discusses each layer in turn. The lowest layers, which implement multicast transport and failure detection, are near completion and currently run on SUN OS using SUN LWP threads, on MACH using C Threads, and on the x kernel [10] ....

K. G. Hamilton, "A Remote Procedure Call System," Ph.D. dissertation, Tech. Rep. no. 70, Computing Laboratory, University of Cambridge, Cambridge, England, December 1984.

....provided by giving a network address, either alongside the procedure interface or later at run time before using the stubs. Also, a number may be used which identifies the desired procedure at that server. This is the solution adopted by many RPC mechanisms including Sun RPC [Sun90] Hamilton [Ham84] extended the syntax for calling a remote procedure to accept a server address. Network objects [BNOW93] on the other hand, always know where to direct the call, because the remote reference to an object includes information about its location. Having this information embedded within the ....

....also be extracted from the program text itself at compile time, but our scheme is more flexible in that it supports creating client and server stubs at any time. 4.2 Using the Generated Stubs After generating the stubs, the programmer then needs to use them from within the language. Hamilton [Ham84] decided to extend the language with special syntax for calling the remote procedures; he argues that extending the language adds extra syntax for RPC control information (such as server binding and error handling) and also emphasizes the semantic distinction between calls to local and remote ....

K.G. Hamilton. A Remote Procedure Call System. PhD thesis, University of Cambridge Computer Laboratory, 1984.

....provided by giving a network address, either alongside the procedure interface or later at run time before using the stubs. Also, a number may be used which identifies the desired procedure at that server. This is the solution adopted by many RPC mechanisms including Sun RPC [13] Hamilton [8] extended the syntax for calling a remote procedure to accept a server address. Network objects [4] on the other hand, always know where to direct the call, because the remote reference to an object includes information about its location. Having this information embedded within the interface or ....

....also be extracted from the program text itself at compile time, but our scheme is more flexible in that it supports creating client and server stubs at any time. 4.2 Using the generated stubs After generating the stubs, the programmer then needs to use them from within the language. Hamilton [8] decided to extend the language with special syntax for calling the remote procedures; he argues that extending the language adds extra information for RPC control (such as server binding and error handling) and also emphasizes the semantic distinction between calls to local and remote procedures. ....

K.G. Hamilton. A Remote Procedure Call System. PhD thesis, University of Cambridge Computer Laboratory, 1984.

....if one of these copies is updated, the other now represents an older state of the object. 4. 1 Examples of Parameter Passing by Copy Most RPC systems pass parameters by copy, including the first RPC mechanism proposed by Birrel and Nelson [BN84] Hamilton s RPC designed for partial failures [Ham84] Argus [Lis88] the RPC products from Sun [Sun90] and OSF [Ope91] XEROX s heteronegeous ILU [JSS94] and our persistent type safe RPC [MdS95] Napier88 RPC [MdS95] is a type safe persistent RPC mechanism for the persistent programming language Napier88 [MBC 94, KBC 94] based on Sun RPC ....

K.G. Hamilton. A Remote Procedure Call System. PhD thesis, University of Cambridge Computer Laboratory, 1984.

....obtained but other mechanisms may also be efficiently supported. A promising set of primitives has been suggested for ACTA [Ramamritham and Chrysanthis, 1992] and its use is being investigated as CACS [Stemple and Morrison, 1992] Other languages, such as Concurrent CLU [Liskov et al. 1981; Hamilton, 1984; Cooper and Hamilton, 1985] and Argus [Liskov, 1984] have explored different concurrency provision. The primitives for distribution have also to be chosen. Candidates may be found in Emerald [Black et al. 1987] Argus, Hermes [Strom et al. 1991] and Guide [Riveill, 1992] A major choice is ....

K.G. Hamilton. A Remote Procedure Call System. PhD thesis, University of Cambridge Computer Laboratory, 1984.

No context found.

Hamilton 84 Hamilton, K.G. "A Remote Procedure Call System," Technical Report No. 70, Computing Laboratory, University of Cambridge, 1984.

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