OSF DCE Application Development Guide--Core Components

OSF DCE Application Development Guide—Core Components
rpc_server_use_all_protseqs (max_calls,
&RPCstatus);
/* This routine is called to obtain a vector of binding
* handles that were established with registration of
* protocol sequences.
*/
rpc_server_inq_bindings (&bind_vector,
&RPCstatus);
/* This routine adds the address information of the binding
* handle for the TP server to the endpoint mapper database.
*/
rpc_ep_register (time_provider_v1_0_s_ifspec,
bind_vector,
NULL,
"Time-Provider",
&RPCstatus);
/* Obtain the name of the machine’s principal and register an
* authentication service to use for authenticated remote
* procedure calls coming from the time service daemon.
*/
dce_cf_prin_name_from_host (NULL,
&machinePrincipalName,
&status);
rpc_server_register_auth_info (machinePrincipalName,
rpc_c_authn_dce_private,
NULL,
NULL,
&RPCstatus);
/* This routine is called to listen for remote procedure calls
* sent by the DTS client. Possible RPC calls coming from DTS
* client are ContactProvider and ServerRequestProviderTime.
*/
rpc_server_listen (max_calls,
&RPCstatus);
20.4 Time-Provider Algorithm
The time-provider algorithm assumes that the two remote procedure calls will come in
the following order: ContactProvider followed by ServerRequestProviderTime. The
algorithm to create a generic time-provider follows:
20 − 10 Tandem Computers Incorporated 124245