| Previous | Table of Contents | Next |
For DCE-CIOP to be used to invoke operations on an object, the information necessary to reference an object via DCE-CIOP must
be included in an IOR. This information can coexist with the information needed for other protocols such as IIOP. DCE-CIOP
information is stored in an IOR as a set of components in a profile identified by either TAG_INTERNET_IOP or TAG_MULTIPLE_COMPONENTS.
Components are defined for the following purposes:
• To identify a server process via a DCE string binding, which can be either fully or partially bound. This process may be a server process implementing the object, or it may be an agent capable of locating the object implementation.
• To identify a server process via a name that can be resolved using a DCE nameservice. Again, this process may implement the object or may be an agent capable of locating it.
• In the TAG_MULTIPLE_COMPONENTS profile, to identify the target object when request messages are sent to the server. In the TAG_INTENET_IOP profile, the object_key profile member is used instead.
• To enable a DCE-CIOP client to recognize objects that share an endpoint.
• To indicate if the pipe-based DCE-RPC interface is not available.
The IOR is created by the server ORB to provide the information necessary to reference the CORBA object.