Community
Participate
Working Groups
An active UI callback is usually deactivated from a background thread. This leads to code like this: UICallBack.runNonUIThreadWithFakeContext( display, new Runnable() { public void run() { UICallBack.deactivate( "foo" ); } } ); I suggest to provide a new method UICallBack#activate( Display, String ) to avoid the above code. The new method would run UICallBack.deactivate( String ) in the context of the given display.
This will probably become obsolete with fixing bug 392976.
The new ServerPushContext can be stopped from a background thread (see bug 392976).