[omniORB] Thread Policy

[Duncan Grisby]

On Monday 18 November, jorgefm@cirsa.com wrote:

> I think that i have found a configuration that works for me with
> 'maxServerThreadPerConnection=1' (the default in omniORB 3.x, i think?)
> The 'call order' is achieve processing all the request from a client in
> the same thread. Before, if the server was busy, the ORB creates a thread
> per request and put them to sleep, but when the server becomes available
> again, all the threads are wake up and you can assure the order easily.

If the client is multi-threaded, it will open new network connections
to the server, so multiple threads will contact your servant
concurrently.  I don't know if that is an issue for you.

Cheers,

Duncan.

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