Previous Table of Contents Next


5.2 Client View

   From a client’s perspective it is only necessary to locate three persistent CORBA singletons implementing ResourceQueryService, ResourceIDService, and ResourceEventSource respectively. Together, these services constitute a data provider.

   The client locates the three services in a single CosNaming::NamingContext within the CORBA Naming service. The location of this NamingContext must be configurable for each instance of the client implementation.

   The client resolves the three services using the following standard names.

Service

Name

Kind

ResourceQueryService “resource_query_service? “?
ResourceIDService “resource_id_service? “?
ResourceEventSource “resource_event_source? “?