[omniORB] Curious omniNames Behavior

[Ken Feuerman]

Thanks Bjorn & Steven for your replies.

Both of you mentioned the Win32 Registry entry for recording the IOR
generated in the start call to omniNames.  True that I haven't been
recording that entry into the registry, because I'm working with another
ORB that also must get a hold of the NameService root context (I record the
root context IOR into a "well-known" file, and all processes in my system
know to look there regardless of which ORB they're using).

But what's curious is that this problem of generating a localhost-based IOR
has never come up before on machines with fixed IP addresses, only on
DHCP-based machines.  In other words, on hosts with fixed IP addresses, I
can omit the registry entry for the NameService, yet still always generate
a correct (non-127.0.0.1) IOR.

The real question I have is:  Suppose I have the situation where omniNames
is restarted on Machine A displaying this localhost-based IOR.  Suppose
further that I have a hold of the original IOR with the correct IP address
encoded from the time when the omniNames was originally started.  Should I
expect this behavior where processes on Machine A can indeed contact the
NameService using the original IOR, but processes on some remote Machine B
can't (using the same original IOR)?

Thanks for your advice/help!

--Ken Feuerman.