Can be found in multiple places. The real WTF, registered listeners are invoked by the business logic by presynchronizing on the SWT Thread so that the GUI must not handle this stuff. Well yes ... just hand out our students a slide describing what is the GUI main thread and how it should handle calls from the business logic. This includes the whole activity stuff. The activites are executed in the Dispatch Thread ... now via the PacketDispatcher which is still a single Thread Executor, there is no need that the Saros Session have to sync on the SWT Thread.
TODO: Review the big comment on the SarosSession class, its description is still wrong. Analyse why the the VCSActivities must be synchronize on the SWT Thread instead of just executing async. Changing the line from Utils.runSafeSync to Utils.runSafeAsync results in approx. 20% - 40% better execution time. Even if the VCSActivities must be synchronized, only synchronize those, but not all activites. Regards, Stefan ------------------------------------------------------------------------------ For Developers, A Lot Can Happen In A Second. Boundary is the first to Know...and Tell You. Monitor Your Applications in Ultra-Fine Resolution. Try it FREE! http://p.sf.net/sfu/Boundary-d2dvs2 _______________________________________________ Dpp-devel mailing list Dpp-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dpp-devel
