Chapter 6 Introduction to RPC

This is the shared library, which provides the functionality of different RPC APIs. It maintains and manages memory for the RPC application. Runtime basically is the transparent layer, which manages the communication with a remote machine in the network. Along with the help of IDL, runtime makes the RPC protocol possible on a heterogeneous network. The data sent across the network are "Marshalled" before being sent and "Unmarshalls" the incoming data. The functions to do these activities are present in the runtime library.

This is the RPC endpoint mapper daemon. RPCD is a process that provides services for the local host, and is also the server used by remote applications to access these host services. The endpoint mapper service maintains a database called the local endpoint map, which allows DCE clients to find servers, individual services provided by servers, and objects managed by services on the host. The endpoint mapper service maps interfaces, object UUIDs, and protocol sequence registrations to server ports (endpoints). Servers register their bindings with the local endpoint mapper, and the endpoint mapper service on each host uses the local endpoint map to locate a compatible server for clients that do not already know the endpoint of a compatible server.

Interface definition language compiler. IDL compiler to converts an interface definition, written in IDL, into output files. The output files include a header file, server stub file, client stub file, and auxiliary files. The compiler constructs the names of the output files by keeping the basename of the interface definition source file but replacing the filename extension with the new extension (or suffix and extension) appropriate to the newly generated type of output file. For example, math.idl could produce math_sstub.c or math_sstub.o for the server stub. IDL compiler generates the "stubs" which, when linked with the appropriate modules of the application, makes the RPC communication simple.