| A. D. Stoyenko, `SUPRA-RPC: SUbprogram PaRAmeters in Remote Procedure Calls', Proc. 3rd IEEE Symposium on Parallel and Distributed Processing, Dallas, TX, December 1991. |
....where a single mobile agent moves to the dynamically selected proxy site, and sends out child agents as needed. There are other forms of mobile code that could be used instead of mobile agents, such as remote evaluation (REV) SG90] SUPRA RPC (SUbprogram PaRAmeters in Remote Procedure Calls) Sto94] and Java servlets [Cha96] 15 Typically, systems that support these forms of mobile code allow one hop migration only. A program is sent to and executed on a target machine, but that program can not send out sub programs. Some systems do allow a program to send out sub programs, but this ....
A. D. Stoyenko. SUPRA-RPC: SUbprogram PaRAmeters in Remote Procedure Calls. Software{ Practice and Experience, 24(1):27-49, January 1994.
....of REV and NCL were primarily concerned with moving computation to a remote machine and imposed this limitation to simplify implementation. SURPRA RPC (SUbprogram PaRAmeters in Remote Procedure Calls) on the other hand seeks to allow normal procedure call semantics for both local and remote calls [Sto94]. Essentially SUPRARPC extends traditional RPC with additional stubs that are invoked whenever a procedure references an out of scope variable or function. The server makes a callback to the client in order to handle the outof scope reference. SUPRA RPC implementations exist for C, C and Lisp ....
A. D. Stoyenko. SUPRA-RPC: SUbprogram PaRAmeters in Remote Procedure Calls. SoftwarePractice and Experience, 24(1):27--49, January 1994.
.... other techniques include message passing, remote procedure calls (RPC) BN84] remote object method invocation (as in Java RMI [WRW96] or CORBA [BN95] queued RPC [JdT 95] in which RPC calls are queued for later invocation if the network connection is down) remote evaluation [Fal87, SG90, Sto94] which extends RPC by allowing the client to send the procedure code to the server, rather than just the parameters for an existing procedure) process migration [DO91, LS92] stored procedures (such as [BP88] where SQL procedures can be uploaded into a relational database for later ....
A. D. Stoyenko. SUPRA-RPC: SUbprogram PaRAmeters in Remote Procedure Calls. Software-- Practice and Experience, 24(1):27--49, January 1994.
....to a server process is structured to give synchronization semantics at the client 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 ....
A. Stoyenko. SUPRA-RPC: SUbprogram PaRAmeters in Remote Procedure Calls. Software, practice & experience, 24(1):27--49, Jan 1994.
....The program chooses when and where to migrate. It can suspend its execution at an arbitrary point, transport to a new machine and resume execution on the new machine. Transportable agents were developed as the next step in the remote procedure call [BN84] remote evaluation [SG90] and SUPRA RPC [Sto94] hierarchy. Transportable agents have several advantages over these paradigms. Transportable agents consume fewer network resources since intermediate data does not need to be brought across the network and agents can communicate easily among themselves. Remote evaluation and SUPRA RPC allow ....
A. D. Stoyenko. SUPRA-RPC: SUbprogram PaRAmeters in Remote Procedure Calls. Software-Practice and Experience, 24(1):27--49, January 1994.
....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 ....
Alexander D. Stoyenko. SUPRA-RPC: SUbprogram PaRAmeters in remote procedure calls. Software Practice and Experience, 24(1):27--49, January 1994.
....mechanism [BN84] Remote programming allows a client to send a subprogram to a server. The subprogram executes on the server and sends its result back to the client. Variants of remote programming include the Network Command Language (NCL) Fal87] Remote Evaluation (REV) SG90] and SUPRARPC [Sto94] Agents generalize remote programming to allow arbitrary code movement. Our system allows agent programmers to choose between a remote conversation (with RPC, message passing, or stream) or a jump followed by a local conversation. Systems such as Java [GM94] Safe Tcl [BR95] and Omniware ....
Alexander D. Stoyenko. SUPRA-RPC: SUbprogram PaRAmeters in Remote Procedure Calls. Software---Practice and Experience, 24(1):27--49, January 1994.
....followed by extensions to the RPC concept, which provided access to certain services in the form of procedure calls from remote locations. Work in this area has included Falcone s Network Command Language (NCL) Fal87] Stamos and Gifford s Remote Evaluation (REV) SG90] and Stoyenko s SUPRA RPC [Sto94]. Each of these systems, however, suffers from a certain inherent lack of flexibility, in that they provide only certain services to remote machines, and do not fit into the model of an intelligent agent. Finally, none of these systems is at all divorced from the client server model of remote ....
Stoyenko, A.D. "SUPRA-RPC: SUbprogram PaRAmeters in Remote Procedure Calls." Software - Practice and Experience, vol. 24, no. 1 (Jan. 1994), pp. 27-49.
....NCL were primarily concerned with moving computation to a remote machine and imposed this limitation to simplify the implementation. SUPRA RPC (SUbprogram PaRAmeters in Remote Procedure Calls) on the other hand, seeks to allow normal procedure call semantics for both local and passed procedures [Sto94] Essentially SUPRA RPC extends REV with additional stubs that are invoked whenever the procedure references an out of scope variable or function. The server makes a callback to the client to handle the out of scope reference. SUPRA RPC implementations exist for C, C and Lisp, but the C and C ....
A. D. Stoyenko. SUPRA-RPC: SUbprogram PaRAmeters in Remote Procedure Calls. Software--Practice and Experience, 24(1):27--49, January 1994.
....process is structured to give synchronization semantics at the client 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] RSV94] and SUPRA RPC [Sto94] Among the commercial RPC packages released have been Courier from Xerox [Xer81] Sun RPC [Sun88] Netwise RPC from Novell Netware, and NCA from Apollo [Apo89] TA90] gives a survey of work in this area. On the surface, the semantics of RPC seem very simple, yet the reality is that there are ....
A. Stoyenko. SUPRA-RPC: SUbprogram PaRAmeters in Remote Procedure Calls. Software Practice & Experience, 24(1):27--49, Jan 1994.
....remotely. In the prototype implementation, the remote programs are a compressed form of list structure executed by a dialect of LISP. Remote procedures must be self contained in that the only external references allowed are to procedures explicitly supported at the remote processing site. Stoyenko [Sto94] describes SUPRA RPC, an extension to RPC which allows subprograms to be passed as RPC parameters. The SUPRA RPC subprograms are allowed to access variables and procedures external to the passed subprogram. These external references are implemented by out of scope access stubs and ....
Stoyenko, A. D. "SUPRA-RPC: SUbprogram PaRAmeters in Remote Procedure Calls." Software--Practice and Experience, vol. 24, no. 1 (Jan. 1994), pp. 27-49.
No context found.
A. D. Stoyenko, `SUPRA-RPC: SUbprogram PaRAmeters in Remote Procedure Calls', Proc. 3rd IEEE Symposium on Parallel and Distributed Processing, Dallas, TX, December 1991.
No context found.
A. Stoyenko, "SUPRA-RPC: SUbprogram PaRAmeters in Remote Procedure Calls," Software-Practice and Experience, Vol. 24, No. 1, pp. 27--49, January 1994.
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