Summary: | API to perform asynchronous resource refresh | ||
---|---|---|---|
Product: | [Eclipse Project] Platform | Reporter: | James Blackburn <jamesblackburn+eclipse> |
Component: | Resources | Assignee: | Platform-Resources-Inbox <platform-resources-inbox> |
Status: | NEW --- | QA Contact: | |
Severity: | enhancement | ||
Priority: | P3 | CC: | ADewar, aleherb+eclipse, amolochnikov, andrew.hunt, angvoz.dev, bhawkes, dak2009, eclipse.sprigogin, jamesblackburn+eclipse, kellyc, malaperle, mober.at+eclipse, rcleveng, recoskie, tparker, wb-rel, wbprio, yevshif |
Version: | 3.6 | Keywords: | api |
Target Milestone: | --- | ||
Hardware: | PC | ||
OS: | All | ||
Whiteboard: | |||
Bug Depends on: | |||
Bug Blocks: | 265504 |
Description
James Blackburn
2010-05-20 04:42:27 EDT
I agree that it would be good to have API for this. In terms of implementation, perhaps it could work to have a special kind of RefreshMonitor which accepts asynchronous refresh requests via the API and enqueues / forwards them to the RefreshManager? 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. |