NAME

rpc_ep_unregister- removes server address information from the endpoint map

SYNOPSIS

#include <dce/rpc.h>

void rpc_ep_unregister(
	rpc_if_handle_t if_handle,
	rpc_binding_vector_t *binding_vec,
	uuid_vector_t *object_uuid_vec,
	unsigned32 *status);

PARAMETERS

Input

if_handle

Specifies an interface specification to remove (that is, unregister) from the endpoint map.

binding_vec

Specifies a vector of binding handles to remove.

object_uuid_vec

Specifies a vector of object UUIDs to remove. The server application constructs this vector. When the value NULL is supplied, the routine constructs the cross-product of if_handle and binding_vec with the nil object UUID.

Output

status

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:

rpc_s_ok

Success.

ept_s_cant_perform_op

Cannot perform requested operation.

DESCRIPTION

An application calls rpc_ep_unregister() to remove endpoint map elements that it has previously registered.

Note:

The application calls the rpc_server_inq_bindings() routine to obtain the required binding_vec argument. To remove selected endpoints, the application can remove individual elements from argument binding_vec before calling this routine.

This routine creates a cross-product from the if_handle, binding_vec and object_uuid_vec arguments, and removes each element that matches the cross-product from the local endpoint map. tagmref_rpc_ep_register discusses the construction of the cross-product.

Matches to elements in the endpoint map are exact. In particular, cross-product elements containing the nil object UUID only match elements in the endpoint map that contain the nil object UUID. Therefore, specifying NULL for the uuid_vec argument results in removing only elements with the nil object UUID from the endpoint map.

Note:

Servers should call rpc_ep_unregister() to unregister their endpoints before they stop running. If they fail to do so, clients may find the obsolete endpoints and waste time trying to communicate with the non-existent servers.

RETURN VALUE

None.

SEE ALSO

rpc_ep_register()
rpc_ep_register_no_replace()
rpc_mgmt_ep_unregister()
rpc_ns_binding_unexport()
rpc_server_inq_bindings().

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.