OSF DCE Application Development Guide--Core Components

OSF DCE Application Development Guide—Core Components

The following calls bind a client to a registry server in preparation for registry

operations. The argument list of these calls enables an application to specify the

authentication protocol, the protection level, and the authorization protocol to be used:

• sec_rgy_site_bind( )

Binds to a speciﬁed site

• sec_rgy_site_bind_update()

Binds to the update site

• sec_rgy_site_bind_query( )

Binds to any query site

• sec_rgy_cell_bind( )

Binds to any registry site in a speciﬁed cell

• sec_rgy_site_binding_get_info( )

Extracts the registry site name and security information from the binding handle

The following calls are similar to the binding calls just described, except that an

application cannot specify security information. By default, however, the following

calls use DCE shared-secret authentication, the packet-integrity level of protection, and

DCE authorization.

• sec_rgy_site_open()

Binds to the speciﬁed site

• sec_rgy_site_open_update( )

Binds to any update site

• sec_rgy_site_open_query()

Binds to any query site

• sec_rgy_site_get( )

Gets the registry site name from the binding handle

The following calls provide miscellaneous binding management functionality:

• sec_rgy_site_close( )

Terminates binding to a registry site and frees resources associated with this binding

• sec_rgy_site_is_readonly()

Tests whether a bound site is an update or query site

27.2 The Registry Database

The registry database comprises three container objects:

27−2 Tandem Computers Incorporated 124245