Remote Procedure Call (RPC) allows constructing distributed applications by extending local procedure calls so the called procedure can exist on a different system. The calling process is suspended, parameters are sent to the remote system, the procedure executes there, then results return to resume the calling process.
Download as PPTX, PDF, TXT or read online on Scribd
0 ratings0% found this document useful (0 votes)
10 views
RPC in Network Management
Remote Procedure Call (RPC) allows constructing distributed applications by extending local procedure calls so the called procedure can exist on a different system. The calling process is suspended, parameters are sent to the remote system, the procedure executes there, then results return to resume the calling process.
Download as PPTX, PDF, TXT or read online on Scribd
You are on page 1/ 7
REMOTE PROCEDURE CALL (RPC)
INTRODUCTION
Remote Procedure Call (RPC) is used for
constructing distributed, client-server based applications. It is based on extending the conventional local procedure calling so that the called procedure need not exist in the same address space as the calling procedure. The two processes may be on the same system, or they may be on different systems with a network connecting them. WORKING OF RPC
1. The calling environment is suspended, procedure parameters
are transferred across the network to the environment where the procedure is to execute, and the procedure is executed there. 2. When the procedure finishes and produces its results, its results are transferred back to the calling environment, where execution resumes as if returning from a regular procedure call. WORKING OF RPC Conceptually, the client and server do not both execute at the same time. Instead, the thread of execution jumps from the caller to the callee and then back again. STEPS DURING A RPC A client invokes a client stub procedure, passing parameters in the usual way. The client stub resides within the client’s own address space. The client stub marshalls(pack) the parameters into a message. Marshalling includes converting the representation of the parameters into a standard format, and copying each parameter into the message. The client stub passes the message to the transport layer, which sends it to the remote server machine. On the server, the transport layer passes the message to a server stub, which demarshalls(unpack) the parameters and calls the desired server routine using the regular procedure call mechanism. STEPS DURING A RPC
When the server procedure completes, it returns to the server
stub (e.g., via a normal procedure call return), which marshalls the return values into a message. The server stub then hands the message to the transport layer. The transport layer sends the result message back to the client transport layer, which hands the message back to the client stub. The client stub demarshalls the return parameters and execution returns to the caller.