Jump to: navigation, search

Mylyn Reviews Architecture (2013)

Revision as of 21:40, 5 February 2013 by Milesparker.gmail.com (Talk | contribs) (New page: This page is intended to organize architectural discussion around proposed improvements to Mylyn Review in the first half of 2013, focussing on high-level architecture rather than specific...)

(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)

This page is intended to organize architectural discussion around proposed improvements to Mylyn Review in the first half of 2013, focussing on high-level architecture rather than specific requirements. (You can find some of the high-level stories here.)

We have a number of tasks for the underlying architectural concerns, but as they're all interrelated, we should capture the current state of design in one place. (Discussion should still take place on related bugs.)

Components

We need to define the basic components of the design and how they'll interact.

Here's a very initial take at a straw person design. (We aren't covering R4E related concerns directly in these diagrams. For example, there is no remote API.)


Key Design Questions

UI Synchronization

What Approach to Synchronization should we take