Abstract
In distributed computing, network sockets provide mechanism for a process to establish a remote connection to another process and send messages back and forth. This interface makes possible a proper mechanism that allows a program running as a process on computer A to call a procedure or a function on remote computer B and pass parameters to it. In the case of synchronous Remote Procedure Call (RPC), processes on computer A need to wait for the finishing of execution of procedures on computer B. When the called procedure finishes, produces its result and passes it to the process on computer A that can continue execution. The question is what happens between the time of the remote procedure call and arrival of the returned values and how much the caller must wait for result. To answer that question, this paper describes the structure of third generation RPCs and analyses them putting the focus on performance and the way of marshalling parameters. To facilitate the choice between them this paper represents the results of performance tests carried out by the authors
Highlights
While developing computer applications, using procedures and functions is very common
Passing by reference is more complex. To enable this technique it is remote procedure calls, the commonly adopted solution is to provide a separate compiler that can generate both the client and server stub functions. The input of this compiler comes from the remote procedure call interfaces written by a programmer
XML-Remote Procedure Call (RPC) does not define any standard methods for generating stub functions or handling remote procedures. It only focuses on messaging and consists of only three small parts: XML-RPC data model is a set of types used in passing parameters, return values, and faults
Summary
While developing computer applications, using procedures and functions is very common. The caller removes the current parameters from the stack, returning it to the original state This method cannot be performed if the callee procedure is stored on a remote computer since there are two different running contexts. To enable this technique it is remote procedure calls, the commonly adopted solution is to provide a separate compiler that can generate both the client and server stub functions. The input of this compiler comes from the remote procedure call interfaces written by a programmer. To enable them for performing stub functions Both the client and the server codes need to be changed to initialize the RPC mechanism
Sign-in/Register to view highlights & summary Sign-in/Register to access full text options 
Free) 
Talk to us
Join us for a 30 min session where you can share your feedback and ask us any queries you have
Schedule a call
