Wt

It can sometimes be hard to know which function access the WApplication. This is annoying for private WResources that are run without taking the application lock. For instance, a paintedWidget that you want to use to create an image may make a call to WApplication::doJavaScript() without the user knowing it, even if the widget is not added to the DOM tree. Using that WPaintedWidget in a private WResource that does not take the application lock may create issues that are hard to debug.

The idea would be to add an option that allows to delete the thread_local WebSession::Handler when the WResource release the application lock. This would also be more consistent with how the application lock actually works when grabbing it using a WApplication::updateLock.