[omniORB] Localhost endpoint: 3.0.4 vs 4.1.0

[Duncan Grisby]

On Thursday 19 July, Mike Richmond wrote:

> With 3.0.4 we initialised the orb with "-ORBpoa_iiop_name_port
> localhost:1234".  Using a port scanning utility we can see port 1234
> is open on addresses 0.0.0.0, 127.0.0.1 and the machine's IP address
> (say 172.1.2.3).

omniORB 3.0.x always listened on all network interfaces. The name is
used purely to choose what to publish in object references.

> With 4.1.0 we initialise the orb with "endPoint
> giop:tcp:localhost:1234".  We now see that port 1234 is open on
> addresses 0.0.0.0 and 127.0.0.1, but not on 172.1.2.3.  Is this
> expected behaviour?  Do we need a second endPoint  to specify
> 172.1.2.3?  Or should we be using "giop:tcp::1234", which seems to
> give the 3.0.4 behaviour?

You should use giop:tcp::1234 to tell omniORB to listen on all
interfaces. omniORB 4.x uses the endPoint specification to choose which
interfaces to listen on, as well as what to publish in object references
(by default).

If you want to publish different addresses to the ones you're listening
on, you should use the endPointPublish parameter in omniORB 4.1.

Cheers,

Duncan.

-- 
 -- Duncan Grisby         --
  -- duncan at grisby.org     --
   -- http://www.grisby.org --