| Previous | Table of Contents | Next |
The baseline transport specified for GIOP is TCP/IP5. Specific APIs for libraries supporting TCP/IP may vary, so this discussion
is limited to an abstract view of TCP/IP and management of its connections. The mapping of GIOP message transfer to TCP/IP
connections is called the Internet Inter-ORB Protocol (IIOP).
IIOP 1.0 is based on GIOP 1.0.
IIOP 1.1 can be based on either GIOP 1.0 or 1.1. An IIOP 1.1 client must support GIOP 1.1, and may also support GIOP 1.0.
An IIOP 1.1 server must support processing both GIOP 1.0 and GIOP 1.1 messages.
IIOP 1.2 can be based on any of the GIOP minor versions 1.0, 1.1, or 1.2. An IIOP 1.2 client must support GIOP 1.2, and may
also support lesser GIOP minor versions. An IIOP 1.2 server must also support processing messages with all lesser GIOP versions.
IIOP 1.3 can be based on any of the GIOP minor versions 1.0, 1.1, 1.2, or 1.3. An IIOP
1.3 client must support GIOP 1.3, and may also support lesser GIOP minor versions. An IIOP 1.3 server must also support processing
messages with all lesser GIOP versions.
Conformance to IIOP versions 1.1, 1.2, and 1.3 requires support of Limited-Profile
IOR conformance (see Section 13.6.2, “Interoperable Object References: IORs,? on
page 13-14), specifically for the IIOP IOR Profile. As of CORBA 2.4, this limited IOR
conformance is deprecated, and ORBs implementing IIOP are strongly recommended to support Full IOR conformance. Some future
IIOP versions could require support of Full IOR conformance.
5. Postel, J., “Transmission Control Protocol – DARPA Internet Program Protocol Specification,? RFC-793, Information Sciences
Institute, September 1981