[omniORB] Connection management behaviour

[David Riddoch]

Hi,


Okay I've done two different solutions.

omniORB 3pre
------------
We allocate connections to threads when they become available, thus we get
the best possible utilisation.

omniORB 2.8
-----------
When all the existing connections are busy and we can't create any new
ones, we allocate a connection at random.  This should be an improvement
over the previous implementation, but won't always be as good as the
above.  The reason I didn't use the same fix as above is that it changes a
number of interfaces, and would break minor version number compatibility.

You can merge the change from 3pre to 2.8 if you really need the best
allocation policy.


Cheers,
David


On Thu, 27 Jan 2000, David Riddoch wrote:

> This is actually a problem with how omniORB allocates connections on the
> client side.  Once we have reached the maximum (5 by default) the orb then
> always allocates the first connection in the list of connections to a
> particular address space, and they then _have_ to proceed serially.
> 
> I'll have a look at doing something about it tomorrow.