The server_rdacl_export Routine

/******
*
* server_rdacl_export -- Make the rdacl interface available
* for ACL editors.
*
*
* Note that we don't export to the namespace. Instead, the ACL editor
* will typically bind to the server via some other entry that holds
* the application-specific interface bindings. This must hold at least
* one object UUID, and the same UUID must be put into the endpoint map
* too. If not, ACL editors will have no way to distinguish the end-
* points of this server from those of other servers on the same host
* that also export the rdacl interface.
*
* Called from main().
*
******/

void server_rdacl_export(
rpc_binding_vector_t *binding_vector, /* Binding handles from RPC runtime. */
uuid_vector_t *object_uuid_vector, /* Server instance UUID(s). */
unsigned32 *status)
{

uuid_vector_t my_uuids;

*status = error_status_ok;

/* Register the server's endpoints with the rdacl interface at the */
/* local endpoint map... */
rpc_ep_register(rdaclif_v1_0_s_ifspec,
binding_vector, /* Our binding handles from RPC runtime. */
object_uuid_vector, /* Server instance UUID (only one). */
(unsigned_char_p_t) "rdacl interface", /* Annotation. */
status);

}