SwingWorker in practice

Question

Sometimes ignorance seems a blessing. I really don't have any problems with my Swing application, a least not yet, until I read: "Long-running computations or input/output (I/O) bound tasks should never run on the Swing EDT." My application has plenty of database interaction, albeit no long-running tasks. However, since all network communication is potentially slow, I guess that the rule also applies to fast stored procedure calls.
I see myself now faced with a huge amount of SwingWorker classes, one for every DAO call, for example:
protected List<Foo> doInBackground() {
        DAOFactory fac = DAOFactory.getInstance();
        FooDAO dao = fac.getFooDAO();
        return dao.getFoos();
}Much of my code is now concerned with SwingWorkers and adding PropertyChangeListeners to these, which make me wonder if everybody takes this rule so literally or that a more pragmatic approach will also do. In other words, do you program for the worst case or for business as usual? Perhaps there is a better way of dealing with SwingWorkers? I am looking forward to your view and experiences on this matter.

Answer 1

Sometimes ignorance seems a blessing. I really don't have any problems with my Swing application, a least not yet, until I read: "Long-running computations or input/output (I/O) bound tasks should never run on the Swing EDT." My application has plenty of database interaction, albeit no long-running tasks. However, since all network communication is potentially slow, I guess that the rule also applies to fast stored procedure calls.
I see myself now faced with a huge amount of SwingWorker classes, one for every DAO call, for example:
protected List<Foo> doInBackground() {
        DAOFactory fac = DAOFactory.getInstance();
        FooDAO dao = fac.getFooDAO();
        return dao.getFoos();
}Much of my code is now concerned with SwingWorkers and adding PropertyChangeListeners to these, which make me wonder if everybody takes this rule so literally or that a more pragmatic approach will also do. In other words, do you program for the worst case or for business as usual? Perhaps there is a better way of dealing with SwingWorkers? I am looking forward to your view and experiences on this matter.