Hey Koen, >> [...] >> shown on screen: as soon as the user closes the tab, the >> wt server detects this event and properly deallocates the >> session without waiting for the timeout to expire. > > You actually see a difference in the same browser with a dialog open > or not for the session to be released? Then that is a bug.
yes, that is definitely the case! Hope you have the chance to reproduce and fix it. >> 3) Also, would it be possible to detect thread pool exhaustion at >> code-level, avoiding the user being stuck waiting for a timeout >> to happen? > > Actually, there is no reason to lock a thread while showing modal > dialogs. You can also show a modal dialog by using show(), and binding > listeners to its accept(), reject() or done() methods. The behavior is > the same, but it is a bit less convenient to implement. Yes, agreed. Just a matter of convenience, indeed. > Regards, > koen Thanks for your explanations. Bye, Antonio ------------------------------------------------------------------------------ BlackBerry® DevCon Americas, Oct. 18-20, San Francisco, CA Learn about the latest advances in developing for the BlackBerry® mobile platform with sessions, labs & more. See new tools and technologies. Register for BlackBerry® DevCon today! http://p.sf.net/sfu/rim-devcon-copy1 _______________________________________________ witty-interest mailing list witty-interest@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/witty-interest
