NAME

rpc_server_use_all_protseqs - Tells the RPC runtime to use all supported protocol sequences for receiving remote procedure calls

Used by server applications. 

SYNOPSIS

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

unsigned32 max_call_requests ,
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 than 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. 

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_cant_create_socket
Cannot create socket.

rpc_s_max_descs_exceeded
Exceeded maximum number of network descriptors.

rpc_s_no_protseqsNo supported protocol sequences. 

DESCRIPTION

The rpc_server_use_all_protseqs routine registers all supported protocol sequences 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 a dynamic endpoint that the RPC runtime and operating system generated. 

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

After registering protocol sequences, a server typically calls the following routines:

rpc_server_inq_bindings
Obtains a vector containing all of the server’s binding handles.

rpc_ep_registerRegisters the binding handles with the local endpoint map. 

rpc_ep_register_no_replace
Registers the binding handles with the local endpoint map.

rpc_ns_binding_exportPlaces the binding handles in the name service database for access by any client. 

rpc_binding_vector_free
Frees the vector of server binding handles.

rpc_server_register_ifRegisters with the RPC runtime those interfaces that the server offers. 

rpc_server_listenEnables the reception of remote procedure calls. 

To selectively register protocol sequences, a server calls the rpc_server_use_protseq, rpc_server_use_all_protseqs_if, rpc_server_use_protseq_if, or rpc_server_use_protseq_ep 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_from_string_binding(3), rpc_binding_to_string_binding(3), 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_if(3), rpc_server_use_protseq(3), rpc_server_use_protseq_ep(3), rpc_server_use_protseq_if(3)