[omniORB] thread policy per interface function

[Duncan Grisby]

On Friday 17 August, Thomas Lockhart wrote:

> > I want part of its functions to be executed single-threaded
> > or multi-threaded (ORB_CTRL_MODEL). But I always want
> > the other part to be executed multi-threaded.
> 
> Given your constraints, I would think that protecting some execution
> paths with a mutex held within your server code would give you the
> single-threaded behavior you need. Leave the mutex out for those
> methods which can be executed in parallel.
> 
> 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.

Cheers,

Duncan.

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