[omniORB] A multi-thread question

[=?GBK?B?wt4=?=]

Dear Duncan, Thanks for your reply. As you said omniORB just use 'manually' and explicitly activated servants(one or more) to service all incoming concurrent requests. So, what isthe good to use thread pool? I mean, all concurrent requests must wait inqueue for the servants to be idle, which is just like all concurrentrequests waiting on the same connection or the same thread. Does every worker thread from thread pool include the servant activated?What if there are serveral different servants? Do I have to enalblemore POAs to deal with them? I don't know the thread model once the ORB gets running. The servant isa single thread? The main thread just listens on the endpoints and dispatchrequests to worker thread? What source files should I refer to? Thanks. Thierry from Beijin, China  
ÔÚ2007-12-21£¬"Duncan Grisby" <duncan at grisby.org> дµÀ£º
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 at grisby.org -- -- http://www.grisby.org --
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://www.omniorb-support.com/pipermail/omniorb-list/attachments/20071222/143ce38b/attachment.htm