On Tue, Sep 20, 2011 at 11:51 PM, Wim Dumon <[email protected]> wrote:
> The proper solution is not to use recursive event loops. You can avoid
> them even when you use modal dialogs, and it's only a little more
> programming work. It will eliminate this 'exhausted thread pool'
> problem completely. Recursive event loops don't really scale with
> concurrent sessions.
I believe that's the only solution. We understood this scaling problem
about the recursive event loop too late...
We have to change part of codes like:
example::onRun() {
<prepare the work>
modal_dialog_asking_are_you_sure.exec();
<run the working thread>
}
in
example::onRun() {
<prepare the work>
<disable wApp>
non_modal_dialog_asking_are_you_sure;
connect_the_dialog_cancel_onCancel;
connect_the_dialog_continue_onContinue;
show();
}
example::onContinue() {
<run the working thread>
}
example::onCancel() {
<enable wApp>
}
G.
--
cpp-today.blogspot.com
------------------------------------------------------------------------------
All the data continuously generated in your IT infrastructure contains a
definitive record of customers, application performance, security
threats, fraudulent activity and more. Splunk takes this data and makes
sense of it. Business sense. IT sense. Common sense.
http://p.sf.net/sfu/splunk-d2dcopy1
_______________________________________________
witty-interest mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/witty-interest
