once again about server port ranges

Some 2 years ago Brent Eagles wrote about subj:



  Just to make sure we are all on the same page... we are talking about 
  specifying a range of 'listening' port numbers, correct?  If so, your 
  cries have been heard.  I'll pass this along for consideration in future 
  releases.  The trick will be in making everybody happy with the fringe 
  conditions, for example:

  * What happens when a server is launched and the ports in the range are 
  exhausted?

  * How much startup overhead is acceptable?  Presumably the whole pool 
  must be searched to find a usable port number.  If the range is large, 
  this may take a few moments.

  * How will this work with the IMR?  I don't know that there would be any 
  issues, but it is something that would need to be looked at.

  Please note that even though the port numbers are constrained for the 
  servers in the 'pool', object references referring to objects hosted in 
  those servers would not be considered persistent since their port 
  numbers could change across process lifetimes.

  Best regards,

  Brent

So if i understand right the situation is following:

1. I can control (-OAPort) listening port number of object adapter.

2. When client call particular service associated with this POA
he(client) is getting _another_ port number to connect to

3. This second port number is out of my control

4. Ergo my corba server cannot serve over firewall??

Regards,
Alexander

_______________________________________________
OB-Users Mailing List - [email protected]
http://mail.ooc.nf.ca/mailman/listinfo/ob-users
Visit our support FAQ before you send a message.
http://www.orbacus.com/faq/support.html