IOP and IIOP interfaces and classes

This section describes the VisiBroker for C++ implementation of the key General Inter-ORB Protocol interfaces and other structures defined by the CORBA specification. For a complete description of these interfaces, refer to the OMG CORBA/IIOP Specification.

IIOP::ProfileBody

struct ProfileBody

This structure contains information about the protocol supported by an object.

module IIOP {
. . .
struct ProfileBody {
GIOP::Version iiop_version;
string host;
unsigned short port;
sequence<octet> object_key;
sequence<IOP::TaggedComponent> components;
};
};

Include file

The IOP_c.hh file should be included when you use this structure.

ProfileBody members

GIPOP::Version iiop_version

The version of IIOP supported.

CORBA::String_var host

The name of the host where the server hosting the object is running.

CORBA::UShort port

The port number to use for establishing a connection to the server hosting the object.

CORBA::OctetSequence object_key

Object keys are stored in a vendor-specific format and are generated when an IOR is created.

IIOP::MultiComponentProfile components

A sequence of TaggedComponents which contain information about the protocols that are supported.

IOP::IOR

struct IOR

This structure represents an Interoperable Object Reference and is used to provide important information about object references. Your client application can create a stringified IOR by invoking the ORB::object_to_string method.

Include file

The IOP_c.hh file should be included when you use this structure.

IOR members

CORBA::String_var type_id

This data member describes the type of object reference that is represented by this IOR.

TaggedProfileSeq profiles

This data member represents a sequence of one or more TaggedProfile structures which contain information about the protocols that are supported.

IOP::TaggedProfile

struct TaggedProfile

This structure represents a particular protocol that is supported by an Interoperable Object Reference (IOR).

Include file

The IOP_c.hh file should be included when you use this structure.

TaggedProfile members

ProfileID tag

The contents of the profile data. Its value should be one of the following:

Value	Description
TAG_INTERNET_IOP	Indicates the protocol is standard IIOP.
TAG_MULTIPLE_COMPONENTS	Indicates the profile data contains a list of VisiBroker ORB services available using the protocol.
TAG_VB_LOCATOR	Indicates that the IOR is an interim, pseudo-object that is used until the real IOR is received by the osagent.
TAG_VSGN_LIOP	Indicates the protocol is IOP over a local IPC mechanism.

CORBA_OctetSequence profile_data

This data member encapsulates all the protocol information needed to invoke an operation on an IOR.