CORBA 2.3.3 Programmer's Guide for C++ (NonStop CORBA 2.3.3+)

Appendix B. Object References
Prev Next
Appendix B. Object References
Table of Contents
Obtaining Object References
Content of Object References
Addresses
NSDOM_GCF_IOP::Profile_Tag Addresses
NSDOM_GFS_IOP::Profile_Tag Addresses
IOP::TAG_INTERNET_IOP Addresses
Configured Versus Actual TCP/IP Addresses
Interoperable Object References for Objects in a Server Pool
IORs for Stateless Objects in a Server Pool
IORs for Stateful Objects in a Server Pool
This appendix contains reference information about object references that some programmers may find
useful as background information, or when debugging. Object references cannot be manipulated directly,
but they are manipulated indirectly when you change configuration settings.
To invoke operations on a distributed object, a NonStop CORBA client uses an Interoperable Object
Reference (IOR). IORs are created by servers. An object reference is communicated to the client and its
contents are known by the client.
A client can treat distributed objects just as it does local objects. A client need not be concerned with the
content of an IOR, but the client must know how to find an IOR and how to release one after using it.
An IOR contains protocol-specific information that NonStop CORBA uses to facilitate communication
between the method invoker (client process) and the method implementer (an object running in a server
process). NonStop CORBA automatically generates object references on behalf of the server process. If
the server process is configured to use more than one protocol (for instance, TS/MP and file system), the
object reference will contain protocol-specific information for each protocol. The protocol-specific
information tells the NonStop CORBA runtime:
How to find the server process when using the specific protocol●
How to find the target object instance within the server process●