NAME

dce_server_enable_service - Enables an individual service for a server

SYNOPSIS

#include <dce/dced.h>
void                                   dce_server_enable_service(
        dce_server_handle_t     server_handle,
        rpc_if_handle_t         interface,
        error_status_t          *status);

PARAMETERS

Input

server_handle

An opaque handle returned by dce_server_register().

interface

Specifies an opaque variable containing information the runtime uses to access interface specification data.

Output

status

Returns the status code from this routine. This status code indicates whether the routine completed successfully. The only status code is error_status_ok.

DESCRIPTION

The dce_server_enable_service() routine enables an individual service that a server provides by registering the service's interface with the RPC runtime, and registering the endpoints in the endpoint map. If the dce_server_c_no_endpoints flag was set with the dce_server_register() call prior to callibng this routine, the endpoints are not registered in the endpoint map.

A server commonly registers all its services with DCE at once by using the dce_server_register() routine. If necessary, a server can use the dce_server_disable_service() routine to disable individual services and then reenable them by using dce_server_enable_service(). However, suppose a server needs its services registered in a certain order, or it require application-specific activities between the registration of services. If a server requires this kind of control as services are registered, you can set the server->services.list[i].flags field of the server_t structure to service_c_disabled for individual services prior to calling dce_server_register(). Then, the server can call dce_server_enable_service() for each service when needed.

RELATED INFORMATION

Routines:   dce_server_disable_service(3dce),    dce_server_register(3dce).

Books: OSF DCE Application Development Guide.