Reports have been coming in that interoperability between TAO and other ORBs is
problematic.

Heinz Haeberle writes:
 >
 >
 > its interesting: it works if server and client are running Linux
 > it works if the server is winnt and the client is JAVA(on win95, jdk1.2 orb)
 > but not with server linux and client JAVA(on win95, jdk1.2 orb)
 >
 > horrible!
 >
 > Heinz
 >
 > >
 > >  ./server -ORBEndpoint iiop://foo:0
 > >
 > > Then simply feed the generated IOR to your client.

Raymond Wiker writes:
	This may be somewhat related:

	I'm trying to get Orbix 3.0c and TAO 5.0 to cooperate. I have
had some success, but I have been completely unable to get TAO to use
Orbix' NameService, and vice versa. To investigate this, I have tried
to use the parseior and catior utilities under
.../ACE_wrappers/TAO/utils.

	The results are *odd*. Using catior on an IOR for TAO's
NameService, I'm told that it is Little Endian, IIOP 1.1. The Orbix NS
is Big Endian, IIOP 1.0, and catior crashes when trying to extract
"Component 0" of the IOR.

	ParseIOR, on the other hand, is unable to make sense of TAO's
NameService IOR, but gives plausible info for Orbix. Plausible, nut
wrong - among other things, it states that Orbix' NameService is at
port 8710 (should be 1570). This appears to be a simple byte-sex
confusion (1570 = 0x0622, 8710 = 0x2206).