RPC: Remote Procedure Call Protocol

	RPC: Remote Procedure Call Protocol
	(RPC: Remote Procedure Call Protocol)

Remote Procedure Call (RPC) is a type of Remote ComputerProgramRequest the service, without understanding the protocol of the underlying network technology. The RPC protocol assumes that some transmission protocols, such as TCP or UDP, carry information data between communication programs. In the OSI network communication model, RPC spans the transport layer and application layer. RPC makes it easier to develop applications, including distributed network applications. RPC adopts the Client/Server mode. A request is a client, and a service provider is a server. First, the calling process sends a call information with process parameters to the service process, and then waits for the response information. On the server side, the process remains asleep until the call information reaches. When a call Information arrives, the server obtains the process parameters, calculates the results, sends the reply information, and waits for the next call Information. Finally, the client receives the reply information during the call process to obtain the process results, then, call and execute to continue. Currently, multiple RPC modes and execution are available. Initially proposed by Sun. The IETF onc Charter revised the sun version, making the onc prc protocol a standard IETF protocol. The most common mode and execution is the distributed computing environment (DCE) based on open software ).

Protocol Structure

The Remote Procedure Call (RPC) Information Protocol consists of two different structures: Call information and reply information. The information process is as follows:

RPC: Remote Procedure Call Process

RPC call information: Each Remote Procedure Call information includes the following unsigned integer fields to identify the Remote Procedure independently: program number program version number procedure number RPC call information subject form: struct call_body { unsigned int rpcvers; unsigned int prog; unsigned int vers; unsigned int proc; opaque_auth cred; opaque_auth Verf; 1 parameter 2 parameter... }; RPC response information: changes in the RPC response information depend on whether the network server receives or rejects the call Information. The reply request includes information about the following situations: call information is successfully executed by RPC .. remote Implementation of RPC is not the second version of the Protocol. The minimum and maximum versions supported by RPC are returned. in a remote system, remote programs are unavailable. the remote program does not support the requested version number. Returns the minimum and maximum versions supported by the remote program. the request process number does not exist. Usually the caller protocol or program error. RPC reply information in the following format: Enum reply_stat stat { msg_accepted = 0, msg_denied = 1 };

Protocols
Organization Source
Related Links	Http://www.javvin.com/protocol/rfc1831.pdf:RPC-Remote Procedure Call Protocol Specification Version 2 (ONC Version) Http://www.javvin.com/protocol/rfc1057.pdf:RPC-Remote Procedure Call Protocol Specification Version 2 (Sun Version) The IEEE defines RPC in its ISO Remote Procedure Call specification, ISO/iec cd 11578 n6561, ISO/IEC, November 1991.