OSF DCE Application Development Guide--Core Components

OSF DCE Application Development Guide—Core Components

= Reference to binding information

Client

Application

Runtime

Importing

Server entry

binding

information

Server

binding

information

Server

binding handle

The callouts in the ﬁgure refer to the following operations:

1. The import operation looks up binding information of a server that is compatible

with the client.

The import operation ﬁnds a server entry based on the speciﬁed interface

identiﬁer, and then looks at the list of object UUIDs. If the importing client

speciﬁes a non-nil object UUID, the import operation looks for and returns that

object UUID. If the client speciﬁes the nil object UUID and the server entry

contains any object UUIDs, the import operation selects and returns one UUID at

random. If the entry lacks any object UUIDs, the import operation returns the nil

UUID.

2. The import operation fetches the compatible binding information and creates a

binding handle for each potential binding represented in the binding information.

3. The import operation then selects a binding handle at random and passes it to the

client application.

13.3.2 UsingString Bindings to Obtain Binding Information

To use a string binding, a client starts with either an existing string binding or with the

components of the binding information. Do not hardcode string bindings into application

code. Rather, specify them at runtime using a command argument, environment

variable, ﬁle, or other means. The simplest way to specify a string binding is for a user

to supply a string binding manually to a client. However, this manual approach is

awkward for users who must know how to obtain and manipulate the string bindings.

13 −12 Tandem Computers Incorporated 124245