Bug 234199 - [repo] need batching mechanism for events
Summary: [repo] need batching mechanism for events
Status: RESOLVED WONTFIX
Alias: None
Product: Equinox
Classification: Eclipse Project
Component: p2 (show other bugs)
Version: 3.4   Edit
Hardware: PC Windows XP
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: P2 Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords: api
: 236498 (view as bug list)
Depends on:
Blocks:
 
Reported: 2008-05-27 13:23 EDT by Susan McCourt CLA
Modified: 2020-02-21 00:47 EST (History)
1 user (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Susan McCourt CLA 2008-05-27 13:23:44 EDT
Today, if you load a repo that references a bunch of other repos (see bug #234177), you will get an add event for every repo added while the load is happening.  The UI refreshes when this happens.  (It could be a *little* smarter here when showing things in site view, but in category and name view, it has to refresh the entire view.)

Since the UI will refresh after the load is over, there's no need for it to try to refresh the view on every interim load.

It would be nice to have some kind of batching API so that a caller could suppress all events until their runnable is complete.  Of course this requires some kind of delta description.

Another possibility would be that the events carry more contextual information so the UI would know what to ignore.  (For example, if I know is happening because of a load, I know I can ignore it).
Comment 1 Susan McCourt CLA 2008-06-10 19:23:56 EDT
*** Bug 236498 has been marked as a duplicate of this bug. ***
Comment 2 Eclipse Webmaster CLA 2019-09-06 16:06:55 EDT
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet.

If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant.
Comment 3 Ed Merks CLA 2020-02-21 00:47:56 EST
There is little UI that ever is updated based on such events, so I don't see a real need for this today.