rpc_server_inq_bindings(3) — Subroutines

NAME

rpc_server_inq_bindings - Returns binding handles for communication with a server

Used by server applications.

SYNOPSIS

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

rpc_binding_vector_t ∗∗binding_vector ,
unsigned32 ∗status );

PARAMETERS

Input

None.

Output

binding_vectorReturns the address of a vector of server binding handles.

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_no_bindings
No bindings.

DESCRIPTION

The rpc_server_inq_bindings routine obtains a vector of server binding handles. Binding handles are created by the RPC runtime 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. The rpc_intro(3) reference page contains an explanation of dynamic and well-known endpoints.

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.

If there are no binding handles (no registered protocol sequences), this routine returns the rpc_s_no_bindings status code and returns the value NULL to argument binding_vector.

The server is responsible for calling the rpc_binding_vector_free routine to deallocate the memory used by the vector.

RETURN VALUES