NAME

rpc_server_use_all_protseqs_if - Tells the RPC runtime to use all the protocol sequences and endpoints specified in the interface specification for receiving remote procedure calls

Used by server applications. 

SYNOPSIS

#include <dce/rpc.h>
void rpc_server_use_all_protseqs_if(

unsigned32 max_call_requests ,
rpc_if_handle_t if_handle ,
unsigned32 ∗status );

PARAMETERS

Input

max_call_requestsSpecifies the maximum number of concurrent remote procedure call requests that the server can accept.  The RPC runtime guarantees that the server can accept at least this number of concurrent call requests.  The actual number of these requests can be greater that the value of max_call_requests and can vary for each protocol sequence.  Use the value rpc_c_protseq_max_reqs_default to specify the default argument value.  Also, routine rpc_server_listen limits (according to its max_calls_exec argument) the amount of concurrent remote procedure call execution.  See the description section of reference page rpc_server_listen(3) for more information. 

if_handleSpecifies an interface specification containing the protocol sequences and their corresponding endpoint information to use in creating binding handles.  Each created binding handle contains a well-known (nondynamic) endpoint contained in the interface specification. 

Output

statusReturns the status code from this routine.  This status code indicates whether the routine completed successfully or, if not, why not.  The possible status codes and their meanings are as follows:

rpc_s_okSuccess. 

rpc_s_calls_too_large_for_wk_ep
Maximum concurrent calls too large.

rpc_s_cant_bind_socketCannot bind to socket. 

rpc_s_cant_create_socketCannot create socket. 

rpc_s_cant_inq_socketCannot inquire endpoint from socket. 

rpc_s_invalid_endpoint_format
Invalid endpoint format.

rpc_s_invalid_if_handleInvalid interface handle. 

rpc_s_max_descs_exceededExceeded maximum number of network descriptors. 

rpc_s_no_protseqsNo supported protocol sequences. 

DESCRIPTION

The rpc_server_use_all_protseqs_if routine registers all protocol sequences and associated endpoint address information provided in the IDL file with the RPC runtime.  A server must register at least one protocol sequence with the RPC runtime to receive remote procedure call requests. 

For each protocol sequence registered by a server, the RPC runtime creates one or more binding handles.  Each binding handle contains the well-known endpoint specified in the IDL file. 

The max_call_requests argument allows you to specify the maximum number of concurrent remote procedure call requests the server handles. 

If you want to register selected protocol sequences specified in the IDL, your server uses the rpc_server_use_protseq_if routine. 

The explanation of the rpc_server_use_all_protseqs routine contains a list of the routines a server typically calls after calling this routine.  (However, a server that uses only routine rpc_server_use_all_protseqs_if does not subsequently call the rpc_ep_register or rpc_ep_register_no_replace routine.)  For an explanation of how a server can establish a client-server relationship without using the local endpoint map or the name service database, see the explanation of a string binding in the rpc_intro(3) reference page. 

RETURN VALUES

None. 

RELATED INFORMATION

Functions: rpc_binding_vector_free(3), rpc_ep_register(3), rpc_ep_register_no_replace(3), rpc_ns_binding_export(3), rpc_server_inq_bindings(3), rpc_server_listen(3), rpc_server_register_if(3), rpc_server_use_all_protseqs(3), rpc_server_use_protseq(3), rpc_server_use_protseq_ep(3), rpc_server_use_protseq_if(3)