OSF DCE Application Development Guide--Core Components

RPC and Other DCE Components
with many RPC resources should usually have each server create a single server
entry for itself and export the object UUIDs of the resources it offers to that server
entry. For example, an application that accesses a different personal calendar for
every member of an organization needs to avoid using a separate server entry for
each calendar.
For some applications, however, you can use a separate server entry for each object
UUID; for example, a print server application that supports a small number of file
formats. Each server can create a separate server entry for each supported file
format and export its object UUID to that server entry. The server entries for a file
format are members of a distinct group.
To import binding information for a server that supports a required file format, a
client specifies the nil UUID as the object UUID and the group for that format as the
starting entry. The import operation selects a group member at random and goes to
the corresponding server entry. Along with binding information, the operation
returns the server’s object UUID for the requested file format from the server entry.
When the client issues a remote procedure call to the server, the imported object
UUID correctly identifies the file format the client needs. Figure 14-19 illustrates
this use of object UUIDs.
124245 Tandem Computers Incorporated 14− 49