The standard interfaces are divided into top level, intermediate level, expert level, and bottom level. These interfaces give a developer much greater control over communication parameters such as the transport being used, how long to wait beforeresponding to errors and retransmitting requests, and so on.
At the top level, the interface is still simple, but the program has to create a client handle before making a call or create a server handle before receiving calls. If you want the application to run on all transports, use this interface. Use of these routines and code samples can be found in "Top Level Interface".
Table 2-2 RPC Routines--Top Level
Routine |
Description |
---|---|
Generic client creation. The program tells clnt_create() where the server is located and the type of transport to use. |
|
Similar to clnt_create() but lets the programmer specify the maximum time allowed for each type of transport tried during the creation attempt. |
|
Creates server handles for all transports of the specified type. The program tells svc_create() which dispatch function to use. |
|
Client calls a procedure to send a request to the server. |
The intermediate level interface of RPC lets you control details. Programs written at these lower levels are more complicated but run more efficiently. The intermediate level enables you to specify the transport to use. Use of these routines and code samples can be found in "Intermediate Level Interface".
Table 2-3 RPC Routines--Intermediate Level
Routine |
Description |
---|---|
Creates a client handle for the specified transport. |
|
Similar to clnt_tp_create() but lets the programmer specify the maximum time allowed. |
|
Creates a server handle for the specified transport. |
|
Client calls a procedure to send a request to the server. |
The expert level contains a larger set of routines with which to specify transport-related parameters. Use of these routines and code samples can be found in"Expert Level Interface".
Table 2-4 RPC Routines--Expert Level
The bottom level contains routines used for full control of transport options. "Bottom Level Interface", describes these routines.
Table 2-5 RPC Routines--Bottom Level
Routine |
Description |
---|---|
Creates an RPC client handle for the specified remote program, using a connectionless transport. |
|
Creates an RPC server handle, using a connectionless transport. |
|
Creates an RPC client handle for the specified remote program, using a connection-oriented transport. |
|
Creates an RPC server handle, using a connection-oriented transport. |
|
clnt_call() |