rpc_server_use_protseq_ep- tells the RPC run-time system to use the specified protocol sequence combined with the specified endpoint for receiving remote procedure calls
void rpc_server_use_protseq_ep( unsigned_char_t *protseq, unsigned32 max_call_requests, unsigned_char_t *endpoint, unsigned32 *status);
- Specifies a protocol sequence to register with the RPC run-time system.
Protocol Sequence Stringslists valid protocol sequence identifiers that may be used for this argument.
- Specifies the number of concurrent remote procedure call requests that the server is guaranteed to accept from the transport. The RPC run-time system allocates sufficient network resources to handle this number of concurrent calls.
The RPC run-time system guarantees that the server can accept at least this number of concurrent call requests. The actual number of these requests can be greater than the value of max_call_requests and can vary for each protocol sequence.
The value rpc_c_protseq_max_reqs_default specifies an implementation-dependent default value >=1.
- The rpc_server_listen() routine specifies a max_calls_exec argument that specifies the number of call threads the server will allocate to handle calls. Normally, the values of max_calls_exec and max_call_requests are the same. Servers are guaranteed to support the minimum of max_calls_exec and max_call_requests concurrent remote procedure calls. Applications should not rely on a server handling more than this number.
- Specifies address information for an endpoint. This information is used in creating a binding handle for the protocol sequence specified in the protseq argument. (See
RPC Data Typesfor information on the syntax of the endpoint argument.)
- Returns the status code from this routine. The status code indicates whether the routine completed successfully, or if not, why not.
Possible status codes and their meanings include:
Protocol sequence not supported on this host.
The rpc_server_use_protseq_ep() routine registers a protocol sequence and its specified endpoint address information with the RPC run-time system. A server must register at least one protocol sequence with the RPC run-time system to receive remote procedure call requests. A server can call this routine multiple times to register additional protocol sequences and endpoints.
The max_call_requests argument specifies the number of concurrent remote procedure call requests the server is guaranteed to handle.
- For a list of routines typically called after rpc_server_use_protseq_ep(), see
Please note that the html version of this specification may contain formatting aberrations. The definitive version is available as an electronic publication on CD-ROM from The Open Group.