<DIV>Dear Duncan,</DIV>
<DIV> </DIV>
<DIV>Thanks for your reply.</DIV>
<DIV> </DIV>
<DIV>As you said omniORB just use 'manually' and explicitly activated servants</DIV>
<DIV>(one or more) to service all incoming concurrent requests. So, what is</DIV>
<DIV>the good to use thread pool? I mean, all concurrent requests must wait in</DIV>
<DIV>queue for the servants to be idle, which is just like all concurrent</DIV>
<DIV>requests waiting on the same connection or the same thread.</DIV>
<DIV> </DIV>
<DIV>Does every worker thread from thread pool include the servant activated?</DIV>
<DIV>What if there are serveral different servants? Do I have to enalble</DIV>
<DIV>more POAs to deal with them?</DIV>
<DIV> </DIV>
<DIV>I don't know the thread model once the ORB gets running. The servant is</DIV>
<DIV>a single thread? The main thread just listens on the endpoints and dispatch</DIV>
<DIV>requests to worker thread? What source files should I refer to?</DIV>
<DIV> </DIV>
<DIV>Thanks.</DIV>
<DIV> </DIV>
<DIV>Thierry from Beijin, China</DIV>
<DIV> </DIV>
<DIV> </DIV>
<DIV ></DIV><BR>ÔÚ2007-12-21£¬"Duncan Grisby" <duncan@grisby.org> дµÀ£º<BR>
<BLOCKQUOTE id=isReplyContent style="PADDING-LEFT: 1ex; MARGIN: 0px 0px 0px 0.8ex; BORDER-LEFT: #ccc 1px solid"><PRE>On Friday 21 December, "=?gb2312?B?wt4=?=" wrote:
> omniORB server supports to upcall application codes through multi
> threads. If I have only one servant activated in the main thread, and
> I configured thread pool mode on the server side, does every invoked
> thread incarnate one more servant to serve the incoming requests? Or,
> only one servant serves all threads' incoming requests?
If you just activate one servant, then that single servant will be used
for all the incoming requests concurrently. That's true regardless of
whether you use thread pool mode or the default thread per connection
mode.
In CORBA, the system never automatically incarnates servants for you.
If that's what you want, you must explicitly create and configure a
servant manager.
Cheers,
Duncan.
--
-- Duncan Grisby --
-- duncan@grisby.org --
-- http://www.grisby.org --
</PRE></BLOCKQUOTE>