| Previous | Table of Contents | Next |
An IOR profile supporting DCE-CIOP must include an object key that identifies the object the IOR represents. The object key
is an opaque sequence of octets used as the object_key member in invoke and locate request message headers. In a TAG_INTERNET_IOP
profile, the object_key member of the IIOP::ProfileBody_1_1 structure is used. In a TAG_MULTIPLE_COMPONENTS profile supporting
DCE-CIOP10, a single TAG_COMPLETE_OBJECT_KEY component must be included to identify the object.
The TAG_COMPLETE_OBJECT_KEY component is available for use by all protocols that use the TAG_MULTIPLE_COMPONENTS profile.
By sharing this component, protocols can avoid duplicating object identity information. This component should never be included
in a TAG_INTERNET_IOP profile.
module IOP { // IDL const ComponentId TAG_COMPLETE_OBJECT_KEY = 5;
};
The sequence of octets comprising the component_data of this component is not interpreted by the client process. Its format
only needs to be understood by the server process and any location agent that it uses.
10.Previous DCE-CIOP revisions used a different component.