[omniORB] Single-threaded behaviour changed between omniORB3 & omniORB4?

[jorgefm@cirsa.com]

Hi Donnacha,

>Note also that, while your solution will solve the
>problem when a single client sends multiple requests,
>it will not protect against the scenario where
>multiple clients are connected. Each connection will
>have its own thread which still means that you might
>have unexpected concurrency. Correct?

Yes, it's correct. It was the behaviour i was looking for.
I only wanted to assure that different calls from different
threads of a client were processed in sequence. The
'unexpected' concurrency is easily managed by the server
with mutual exclusion, etc if you have one server and
multiple clients. I don't know if there is another an option
to create only one thread per server object, maybe playing with
'threadPerConnectionPolicy=0' and 'maxServerThreadPoolSize=1' ?
Take a look at chapter 4 and 8 from omniOrb manual.

Hope this helps,
Jorge