rpc_server_inq_bindings- returns binding handles for communication with a server
void rpc_server_inq_bindings( rpc_binding_vector_t **binding_vector, unsigned32 *status);
- Returns the address of a vector of server binding handles.
- 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:
The rpc_server_inq_bindings() routine obtains a vector of server binding handles. Binding handles are created by the RPC run-time system when a server application calls any of the following routines to register protocol sequences:
- rpc_server_use_all_protseqs() rpc_server_use_all_protseqs_if() rpc_server_use_protseq() rpc_server_use_protseq_ep() rpc_server_use_protseq_if()
The returned binding vector can contain binding handles with dynamic endpoints and binding handles with well-known endpoints, depending on which of the above routines 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, or for conversion to string bindings.
When there are no binding handles (no registered protocol sequences), this routine returns the rpc_s_no_bindings status code and returns the value NULL in binding_vector.
The application is responsible for calling the rpc_binding_vector_free() routine to deallocate the memory used by the vector.
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.