After a server passes to the RPC runtime the protocol sequences over which it will listen for remote procedure calls, the RPC runtime constructs server binding handles. Each binding handle refers to a complement of binding information that defines one potential binding; that is, a specific RPC protocol sequence, RPC protocol major version, network address, endpoint, and transfer syntax that an RPC client can use to establish a binding with an RPC server.
Before registering endpoints or exporting binding information, a server must obtain a list of its binding handles from the RPC runtime by using the rpc_server_inq_bindings( ) routine. The server passes this list back to the runtime as an argument when registering endpoints and exporting binding information.