| Previous | Table of Contents | Next |
Object references are encoded in OMG IDL (as described in Section 13.5, “Object
Addressing,? on page 13-11). IOR profiles contain transport-specific addressing
information, so there is no general-purpose IOR profile format defined for GIOP. Instead, this specification describes the
general information model for GIOP profiles
and provides a specific format for the IIOP (see “IIOP IOR Profiles? on page 15-52).
In general, GIOP profiles include at least these three elements:
1. The version number of the transport-specific protocol specification that the server supports.
2. The address of an endpoint for the transport protocol being used.
3. An opaque datum (an object_key, in the form of an octet sequence) used exclusively by the agent at the specified endpoint address to identify the object.