[omniORB] Binding omniORB to a specific address

[Duncan Grisby]

On Thu, 2013-09-05 at 16:16 +0200, Sylvain Gault wrote:

> > I see. The outgoing interface the client uses is determined by the IP
> > stack's routing setup. It's not something that omniORB has any control
> > over. Your operating system probably has a "route" command that lets you
> > configure it. 
> 
> Actually, it can do something about it. The bind(2) function can be used
> on client-side sockets to specify a local address when the system have
> several addresses.

Sorry, I didn't mean to suggest that omniORB couldn't possibly do
anything about it, merely that it has no code to do so at present.
Further, I don't think it's appropriate for a client program to make
such choices -- TCP stacks have routing tables for this purpose, and it
is not a good idea for a client process to try to second-guess the
routing setup.

Cheers,

Duncan.

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