IOR doesn't contain FQDN or IP - can it?

[Jules Colding <colding omesc com>]

Hi,

This seemed so simple... Remote ORBs can't resolve IORs created on my
box. I can see from ior-decode-2 that only the hostname is included in
the IOR:

#### snip ####
colding omc-2 ~/work/src/brutus/idl/samples/C/client $  ior-decode-2 $(cat ior.orbit2)
Object ID: IDL:omc.brutus/BRUTUS/SRestrictionContainer:1.0
IOP_TAG_GENERIC_IOP: GIOP 1.2[UNIX] omc-2:/tmp/orbit-colding/linc-16c2-0-b1210da18a3b
#### snip ####

while the actual IP address is (controlled by an ORB option) used by
e.g. TAO (on the same box):

#### snip ####
colding omc-2 ~/work/src/brutus/idl/samples/C/client $  ior-decode-2 $(cat ior.tao)
Object ID: IDL:omc.brutus/BRUTUS/SRestrictionContainer:1.0
IOP_TAG_INTERNET_IOP: GIOP 1.2 10.0.1.4:32782
    object_key (35) '14010f004e535486f2e342ef3203000100000001000000000000000100000001000000'
#### snip ####


I can not see any way of forcing ORBit2 into using the IP address
instead. It would be really convenient to have an option that will make
the IP address being used instead of the hostname, fully qualified or
not. Using the IP address in the IOR will guarantee that remote ORBs are
able to resolve the object without any configuration changes on the
local box or in the DNS.

I am looking at the source (CVS HEAD) but it is not crystal clear where
the actual IOR is being composed. Could someone point me in the right
direction source-wise please?


Thanks,
  jules