[omniORB] thread policy per interface function

[Thomas Lockhart]

>> The downside is that you will be tying up ORB threads while they wait
>> for the mutex to become free.
> That doesn't make any difference. omniORB implements the single thread
> model with a recursive mutex, so using a mutex in application code is no
> different.

I was assuming a multi-threaded model with individual methods forcing 
single-thread behavior by holding application-level mutexes. Is there a 
fatal flaw in that configuration?

                        - Tom