Important that each addRow be synched with a tableChange event?

Question

Suppose you have a folder that can recieve objects from any thread. The insert method is synchronized, so only one thread gets in at a time. The folder is a TableModel. Each insert needs to update the UI.
If you use invokeAndWait, you run the risk of deadlock when the EDT is waiting for the folder to be free while another thread is blocking on the EDT. One solution is to use invokeLater, but then each UI update doesn't necessarily come immediately after its corresponding insert.
Another solution is to force all inserts to come from the EDT. This solution is less desirable since sometimes the folder is not open, and there is no need to update the UI.
So my question is: How important is it that each table change event follow immediately after the corresponding change to the data model?

Answer 1

I don't think the component will actually update the
gui
everytime you insert data. If you insert many things
in rapid succession, it will probably end up with one
update
at the end.If you're using a DefaultXXXXMode, any change to the model results in an event being fired to listeners. If one of those listeners is a visible view, the component is dirtied and will be redrawn the next time the GUI is refreshed.
You can have rapid inserts, and maybe the GUI will only be redrawn once, but the component will be dirtied every time.
>
Why not modify the table model and add a method that
takes
a block of objects and insert them together instead of
1 by 1?
That will ensure only 1 gui update be dispatched for a
block
of objects inserted. That's what I did in my program.
There is a method
named fireTableRowsInserted(int start, int end) that
you might
want to use.The problem is that the table model is part of a larger model, and there are 3 representations of data that exist in the model. Objects passed into this model are stored in an array (if the model contains a vew that's visible), are also cached, and also sent across a server to be stored remotely. Since objects can be stored into the model from any thread, you must use synchronization to keep it from stepping on itself. A problem occurs when you do an invokeAndWait call from a synchronized method, since the EDT could already be waiting for the object to finish with its current synchronized operation.