[omniORB] Multithreading mechanism

[Yang Lingjia]

Hi,

Should I take it as that OmniOrb doesn't support thread pool mechanism?  :-)

The reason for us to in favor of pool thread mechanism is that  we need to
initialize a pool of database connections at the startup stage of the system.
As we all know that initialization of database handler takes a long time.
This will reduce the waiting time of the clients and we can reuse the
resources.  In the other words, if we use thread per connection mechanism,
database handler will be released after the client disconnected.  If we use the
thread pool mechanism, we can reuse the database handler.  Thread pool
mechanism is more efficient compare to thread per connection because it allows
sharing of threads among clients.

One more point, our clients need to initialize a few request to the server at
one time.  It will have no problem with pool thread mechanism.  For thread per
connection, it needs to initialize a connection per request.

For your comments please!

Lingjia

Sai-Lai Lo wrote:

> >>>>> Yang Lingjia writes:
>
> > We are doing some evaluation on OmniOrb.  I read from some documentation
> > on the web that OmniOrb only supports thread per connection.  Is it
> > true?  How much effort do I need to implement a thread pool mechanism?
>
> I'm curious why you need a thread pool mechanism?
>
> --
> Sai-Lai Lo                                   S.Lo@uk.research.att.com
> AT&T Laboratories Cambridge           WWW:   http://www.uk.research.att.com
> 24a Trumpington Street                Tel:   +44 1223 343000
> Cambridge CB2 1QA                     Fax:   +44 1223 313542
> ENGLAND