Bug 186994 - [apidoc] Document the meaning of RSE Remote Refresh
Summary: [apidoc] Document the meaning of RSE Remote Refresh
Status: NEW
Alias: None
Product: Target Management
Classification: Tools
Component: RSE (show other bugs)
Version: 2.0   Edit
Hardware: All All
: P3 enhancement (vote)
Target Milestone: Future   Edit
Assignee: dsdp.tm.rse-inbox CLA
QA Contact: Martin Oberhuber CLA
URL:
Whiteboard:
Keywords:
Depends on:
Blocks: 173042
  Show dependency tree
 
Reported: 2007-05-15 08:43 EDT by Martin Oberhuber CLA
Modified: 2009-03-18 07:59 EDT (History)
0 users

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Martin Oberhuber CLA 2007-05-15 08:43:30 EDT 
RSE SystemView distinguishes between "local refresh" and "remote refresh", where the latter is done if any element to be refreshed adapts to an ISystemRemoteElementAdapter.

This behavior needs to be documented in the Javadoc of ISystemRemoteElementAdapter, probably also ISystemViewElementAdapter / AbstractSystemViewElementAdapter, and the Refresh Events.

See also bug #186991 comment 1: we'll need to clearly understand the meaning of the internal RSE "Remote Refresh" and why it does the thing it does: collapse nodes, mark folders as stale, remove children. Supposedly, it does this in order to be more efficient by deferring refresh of collapsed folders by marking them stale rather than refreshing them.
Comment 1 Martin Oberhuber CLA 2007-05-15 08:47:36 EDT 
Note that there is also
   ISystemRemoteElementAdapter.refreshRemoteObject(Object old, Object new)
which also seems to play an important role in remote refresh scenarios.
Comment 2 Martin Oberhuber CLA 2008-08-19 10:57:39 EDT 
Will need to clarify RSE Remote Refresh early in 3.1