[omniORB] GIOP 1.1 and omniOrb

[Sai-Lai Lo]

If IBM JDK 1.2 is using GIOP 1.1 to talk to omniNames, it is a bug in JDK.

The choice of what GIOP protocol version to use to talk to a CORBA object
is determined by the information contained in the IOR of the object. In the
case of omniName's root context, it says GIOP 1.0. Therefore the client
(JDK) should not be using GIOP 1.1 to talk to it.

On the otherhand, if the IOR says 1.2, the client is free to use any of the
lower GIOP versions to talk to the object, i.e. 1.1 or 1.0.

omniNames/omniORB will support GIOP 1.1 and 1.2 and bi-direction GIOP.
Now that omniORB 3 is released, the merge of the new GIOP code will
commence. 


Sai-Lai

>>>>> Daniel M Johnson writes:

> I had a problem getting IBM AIX JDK 1.2 talking to omniNames 2.8.0.  Come
> to find out the problem is that IBM was talking GIOP 1.1 and omniNames is
> talking GIOP 1.0.

> Will omniNames/ omniORB use GIOP 1.1 in the future?

> Shouldn't GIOP be backwards compatible?  I mean, is this just a bug in
> IBM's
> code, or do we really need to use ORB's that use the same GIOP versions?

> Any info, or pointers to discussion about this issue would be greatly
> appreciated!