GIOP remote references present you with a transparent view of the referenced CORBA objects. GIOP remote references transparently forward all received messages to the remote objects indicated by their embedded SstIor object. You can use exactly the same message sends you would use if you were programming with local objects or with some other SST by-reference invocation architecture. Remote references are automatically created and managed by SST.
The following instance API method is provided in addition to the usual remote reference methods inherited from SstRemoteReference:
You can create GIOP remote references explicitly from an SstIor object. The operation that does this takes the following form:
The type ID information associated with an IOR may be empty or only partially accurate. In certain circumstances, you might want to perform operations on an object that are not currently known to be supported from the limited type information available. In other systems and language bindings, this is supported by operations to narrow the type information--effectively a form of safe type casting. SST provides support for a similar action with the following API method on SstGiopRemoteReference instances.
Since CORBA supports multiple inheritance of interfaces, GIOP remote references might have more than one type ID associated with them at any one time. Where possible, the most specific type ID information is used when marshaling object references.