Previous | Table of Contents | Next |
Locate request messages may be sent from a client to a server, as the request_message parameter of a locate RPC, to determine
the following regarding a specified object reference:
• Whether the object reference is valid.
• Whether the current server is capable of directly receiving requests for the object reference.
• If not capable, to solicit an address to which requests for the object reference should be sent.
For details on the usage of the locate
RPC, see Section 16.6, “DCE-CIOP Object
Location,? on page 16-21.
Locate request messages contain a fixed-format header, but no body.
16.4.3.1 Locate Request Header
DCE-CIOP locate request headers have the following format:
module DCE_CIOP { // IDL struct LocateRequestHeader { boolean byte_order;
7. Previous revisions of DCE-CIOP returned a MultipleComponentProfile structure. An IOR is now returned to allow either a TAG_INTERNET_IOP or a TAG_MULTIPLE_COMPONENTS profile to be used.
8. An exponential back-off algorithm is recommended, but not required.
sequence <octet> object_key;
string operation;
// no body follows};};
The members have the following definitions:
• byte_order indicates the byte ordering used in the representation of the remainder of the message. A value of FALSE indicates
big-endian byte ordering, and TRUE indicates little-endian byte ordering.
• object_key contains opaque data used to identify the object that is the target of the operation. Its value is obtained from
the object_key field of the TAG_INTERNET_IOP profile or the TAG_COMPLETE_OBJECT_KEY component of the TAG_MULTIPLE_COMPONENTS
profile.
• operation contains the name of the CORBA operation being invoked. It is encoded as in the invoke request header.