Hi all, > Hi all, > I'm getting some strange behavior in my application which has a dialog > showingthe underlying process > [...]
can this strange behaviour be due to the number of threads configured in the corresponding section of the configuration file for the selected http connector? What does this description actually mean (from the comments in the configuration file)? You may want to change this value if you would like to support more reentrant event loops, where you block one event loop using WDialog::exec() or related static methods. Everytime you enter such an event loop, one thread is blocked, and therefore the total number of sessions that reliably can do this is limited to the number of thread you have (minus one to unblock). Does this imply that having more than one session calling a Wt::WDialog::exec() might be a problem? If this is the case, what would you expect to see at browser level? -- Antonio ------------------------------------------------------------------------------ Doing More with Less: The Next Generation Virtual Desktop What are the key obstacles that have prevented many mid-market businesses from deploying virtual desktops? How do next-generation virtual desktops provide companies an easier-to-deploy, easier-to-manage and more affordable virtual desktop model.http://www.accelacomm.com/jaw/sfnl/114/51426474/ _______________________________________________ witty-interest mailing list witty-interest@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/witty-interest