RpcServerInqBindings function
The RpcServerInqBindings function returns the binding handles over which remote procedure calls can be received.
Syntax
RPC_STATUS RPC_ENTRY RpcServerInqBindings( RPC_BINDING_VECTOR **BindingVector );
Parameters
- BindingVector
-
Returns a pointer to a pointer to a vector of server binding handles.
Return value
| Value | Meaning |
|---|---|
|
The call succeeded. |
|
There are no bindings. |
Remarks
A server application calls RpcServerInqBindings to obtain a vector of server binding handles. The RPC run-time library creates binding handles when a server application calls the following functions to register protocol sequences:
- RpcServerUseAllProtseqs
- RpcServerUseAllProtseqsEx
- RpcServerUseAllProtseqsIf
- RpcServerUseAllProtseqsIfEx
- RpcServerUseProtseq
- RpcServerUseProtseqEx
- RpcServerUseProtseqEpEx
- RpcServerUseProtseqIf
- RpcServerUseProtseqIfEx
- RpcServerUseProtseqEp
The returned binding vector can contain binding handles with dynamic endpoints or binding handles with well-known endpoints, depending on which of the above functions the server application called.
A server uses the vector of binding handles for exporting to the name service, for registering with the local endpoint-map database, or for conversion to string bindings. If there are no binding handles (no registered protocol sequences), this routine returns the RPC_S_NO_BINDINGS status code and a BindingVector parameter value of NULL. The server is responsible for calling the RpcBindingVectorFree function to release the memory used by the vector.
Requirements
|
Minimum supported client |
Windows 2000 Professional [desktop apps only] |
|---|---|
|
Minimum supported server |
Windows 2000 Server [desktop apps only] |
|
Header |
|
|
Library |
|
|
DLL |
|
See also
- RpcBindingVectorFree
- RpcEpRegister
- RpcEpRegisterNoReplace
- RpcNsBindingExport
- RpcServerUseAllProtseqs
- RpcServerUseAllProtseqsIf
- RpcServerUseProtseq
- RpcServerUseProtseqEp
- RpcServerUseProtseqIf