RpcServerUseAllProtseqs
The RpcServerUseAllProtseqs
function tells the RPC run-time library to use all supported protocol sequences
for receiving remote procedure calls.
This function
is supported by both 32-bit platforms Windows NT and Windows 95.
For a list of
Microsoft RPC s supported protocol sequences, see the reference topic String
Binding
#include <rpc.h>
RPC_STATUS RPC_ENTRY RpcServerUseAllProtseqs(
unsigned int MaxCalls, |
|
void *
SecurityDescriptor |
|
); |
|
Parameters
MaxCalls
Specifies the
maximum number of concurrent remote procedure call requests the server can
accept.
The RPC
run-time library guarantees that the server can accept at least this number of
concurrent call requests. The actual number can be greater and can vary for
each protocol sequence.
Use
RPC_C_PROTSEQ_MAX_REQS_DEFAULT to specify the default value.
SecurityDescriptor
Points to an
optional parameter provided for the Microsoft Windows NT security
subsystem.Note that this parameter does not appear in the DCE specification for
this API.
Remarks
A server
application calls the RpcServerUseAllProtseqs routine to register all of
the supported protocol sequences with the RPC run-time library. To receive
remote procedure calls, a server must register at least one protocol sequence
with the RPC run-time library.
For each
protocol sequence registered by a server, the RPC run-time library creates one
or more binding handles through which the server receives remote procedure call
requests. The RPC run-time library creates different binding handles for each
protocol sequence. Each binding handle contains an endpoint dynamically generated
by the RPC run-time library or the operating system.
The MaxCalls
argument allows the server to specify the maximum number of concurrent remote
procedure call requests the server wants to be able to handle.
See Server
Application RPC API Calls
To
selectively register protocol sequences, a server calls the RpcServerUseProtseq,
RpcServerUseProtseqIf, or RpcServerUseProtseqEp routine.
Return Values
Value |
Meaning |
RPC_S_OK |
Success |
RPC_S_NO_PROTSEQS |
No
supported protocol sequences |
RPC_S_OUT_OF_MEMORY |
Insufficient
memory available |
RPC_S_INVALID_SECURITY_DESC |
Security
descriptor invalid |
See Also