[concurrency-interest] SwingWorker a special producer/consumer
forax at univ-mlv.fr
Thu Jun 1 04:51:55 EDT 2006
Yesterday, i found a bug in the Sun implementation of the SwingWorker :
Basically a swing worker permits to create a worker thread for
a long duration job that need to perform some refresh of the
swing ui without freezing the application.
Because only the Event Dispatch Thread can change the
swing UI, the worker thread publish data and
the EDT consume them.
It's a special producer/consumer because the EDT consume
all the available data in once.
Which data structure should be used in that case ?
More information about the Concurrency-interest