By aalmiray
via pushing-pixels.org
Published: Jul 16 2008 / 13:16
Most of the newcomers eventually find out that Swing is not thread-safe, but this is most certainly not Swing’s “fault”. Other UI toolkits, such as SWT, Win32 API, Motif, Xlib and GTK are not thread-safe as well (and if you have time, Chet had an interesting overview entry on this topic a few years ago). It’s just that Swing is very lenient on the application code that violates the Event Dispatch Thread rules that state that every interaction with UI component must be done from the single UI thread (EDT). Unlike SWT that is much more rigorous in this aspect (checking access and throwing runtime exceptions), most Swing violations may go unnoticed for a long time, creeping to the production environment and making it very hard to debug / reproduce the scenarios on our development machines.
Add your comment
Voters For This Link (14)
-
aalmiray -
kirillcool -
bloid -
Thierry.Lefort -
ziffdavis -
thinkingserious -
alruiz15 -
wanghy -
WeiLing -
mswatcher -
socker -
adobni -
ixchelruiz -
davneter