OSF DCE Application Development Guide--Core Components

OSF DCE Application Development Guide—Core Components
Each routine is described as follows:
dced_binding_from_rpc_binding()
The dced_binding_from_rpc_binding( ) routine returns a dced binding
handle whose data type is dced_binding_handle_t. This binding handle
is used in all subsequent dced API routines to access the service. The
host is determined from the RPC binding handle, rpc_bh, and the
service_type is selected from the following list:
• dced_e_service_type_hostdata
• dced_e_service_type_srvrconf
• dced_e_service_type_srvrexec
• dced_e_service_type_keytab
dced_list_get()
Applications use the dced_list_get() routine to get a service’s entire list
of names. Using the dced_list_get( ) routine gives your application great
flexibility when manipulating entries in an entry list. If you prefer, your
application can use the dced_entry_cursor_initialize(),
dced_entry_get_next( ), and dced_entry_cursor_release() set of
routines to obtain individual entries, one at a time.
select_entry( )
This is an application-specific routine that selects which entry to use
based on the entry name.
dced_object_read()
The default attribute for dced_object_read( ) is to return an array of
strings. The hostdata and keytab services have other ‘‘read’’ routines
that allow you to specify binary data.
display() This is an example of an application-specific routine that simply displays
the server configuration data read. Depending on the service, a different
data structure is used. For the hostdata service, a sec_attr_t is used.
For the srvrconf and srvrexec services server_t structures are used.
For the keytab service, a dced_key_list_t structure is used.
dced_objects_release()
After your application is finished with the data read with the
dced_object_read() routine, free the buffer of allocated data by using
the dced_objects_release( ) routine.
dced_list_release()
Each call to the dced_list_get( ) routine requires a corresponding call to
dced_list_release() to release the resources allocated for the entry list.
dced_binding_free( )
Each call to the dced_binding_from_rpc_binding() routine requires a
corresponding call to dced_binding_free( ) to release the resources of
the allocated binding.
2− 12 Tandem Computers Incorporated 124245