Bug 204592 - [view model][update policy] Switch from caching IDMData to caching the proposed IPropertiesUpdate objects.
Summary: [view model][update policy] Switch from caching IDMData to caching the propos...
Status: RESOLVED FIXED
Alias: None
Product: CDT
Classification: Tools
Component: cdt-debug-dsf (show other bugs)
Version: 0 DD 1.0   Edit
Hardware: PC Linux
: P3 normal (vote)
Target Milestone: 6.0   Edit
Assignee: Pawel Piech CLA
QA Contact: Pawel Piech CLA
URL:
Whiteboard:
Keywords: api
Depends on: 204587 204588
Blocks: 237557 202656 225650
  Show dependency tree
 
Reported: 2007-09-25 14:19 EDT by Pawel Piech CLA
Modified: 2009-03-10 19:59 EDT (History)
6 users (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Pawel Piech CLA 2007-09-25 14:19:05 EDT
Currently the view updates cache stores IDMData objects which are retrieved directly from services.  The problem with this approach is that the layout nodes which retrieve the IDMData objects from services have to use the update manager object to do so.  In other words the caching cannot be made transparent to the layout nodes.  

Instead the layout nodes should be migrated to implement the proposed IElementPropertyProvider interface, and for the update manager to cache the IPropertyUpdate objects, which would in turn be used by a configurable label provider to generate the label.  This way the IElementPropertyProvider could be implemented without references to the update manager, thus reducing dependencies.
Comment 1 Pawel Piech CLA 2008-02-14 12:29:18 EST
*** Bug 217928 has been marked as a duplicate of this bug. ***
Comment 2 Pawel Piech CLA 2008-04-02 00:25:36 EDT
I think this is too big a change to try to squeeze in in M6.  I could probably complete the implementation in a couple of days, but I would not be able to adequately test it.

Fortunately the API changes needed for this bug are completely backward compatible.  So we can address this bug after 1.0.
Comment 3 Pawel Piech CLA 2009-03-10 19:55:01 EDT
Fixed along with bug 225650.