There are cases in which it is important/necessary to be able to
configure the hostname which the ORB uses when creating IORs for objects
which it implements. We need some mechanism for this -- probably something
equivalent to the java.rmi.server.hostname system property used by RMI.
I would suggest org.omg.CORBA.ORBLocalHost to be consistent with other
existing JavaIDL property names. This could then be passed in to JavaIDL
the same ways as existing configuration properties such as
org.omg.CORBA.ORBInitialHost. The value of this property would be a string
host address representation -- either a DNS-style hostname like
"shimmer.eng.sun.com" or a "dotted decimal" IP address such as "129.144.75.41".

There are at least 2 reasons for this:

1. supplying a fully specified host name in NIS/NIS+ environments
where hostnames obtained via Java's InetAddress.getLocalHost()
return only simple domainless names such as "shimmer". This
is needed if the CORBA objects are to be accessed from another
hostname domain such as someone in east.sun.com accessing
shimmer which is in eng.sun.com.

2. allowing IORs to contain a specific host address for machines
that support multiple IP addresses either as part of virtual hosting
or because of multiple network adapters.