Community
Participate
Working Groups
Summary: The full implementation relies on the implementation of data coalescing Bug 292967, however this implementation will proceed with the support of a single view. The sequence in summary is as follows: 1) Each view is in charge to trigger the notification of external time selection modifications to TMF, 2) TMF itself will broadcast this notification to any interested registered components e.g. other views. 3) TMF shall handle internal notifications to know when the broadcasting of new application events has started and finished 4) The above internal notification will be used to know when data coalescing can proceed. 5) Upon reception of the event notification from TMF to the component / views. a corresponding event data request will be triggered 6) The components / views shall determine the corresponding data provider by querying TMF for it, specifying the information type. 7) The resulting information will be received within the data request object e.g. handleData()
Update: the branch named "provider" incorporated updates from TMF which supports the registration of event providers and the possibility to process sub-request within a provider. A test case was included with the first template implementation to use synthetic event provider.
Merged with trunk.
Delivered with the Helios release.
