OSF DCE Application Development Guide--Core Components

RPC and Other DCE Components
After finding a server entry with compatible binding information for the statistics
interface, the import operation returns an instance UUID along with binding
information. Every remote procedure call made with that binding information goes
to the server instance that exported the instance UUID.
Figure 14-16. Service Model: Distinct Instances on One Host
Report_writer V2.0 interface
Statistics V1.0 interface
Exporting
Name service database
MAYA systemMAYA system
Statistics−service server instance 2Statistics−service server instance 1
Report_writer V2.0 interface
Statistics V1.0 interface
Exporting
/.:/LandS/Statistics_service_MAYA_01
Interface ID for Statistics V1.0
Instance UUID for instance 1
/.:/LandS/Statistics_service_MAYA_02
Instance UUID for instance 2
Interface ID for Statistics V1.0
/.:/LandS/Statistics_service_grp
/.../C=US/O=TheU/OU=MadCity/LandS/Statistics_service_MAYA_01
/.../C=US/O=TheU/OU=MadCity/LandS/Statistics_service_MAYA_02
Target interface:
Target Object:
Starting Entry: /.:/LandS/Statistics_service_grp
Search Requirements
Maximum number of traversed entries:
Statistics V1.0
None
2
14.3.5 The Resource Model for Defining Servers
The resource model views servers and clients as manipulating resources. A server
and its clients use object UUIDs to identify specific resources. With the resource
model, any resource an application’s servers and clients manipulate using an object
UUID is considered an RPC resource. Typically, an RPC resource is a physical
resource such as a database. However, an RPC resource may be abstract; for
example, a print format such as ASCII. Note that an application that uses the
resource model for one context may use the service model for another. (See earlier
sections for details of the service model.)
124245 Tandem Computers Incorporated 14− 43