Background
See #14
Problem
An area map for the various implemented event stream handlers is needed, with careful consideration for the differences between "virtual" and "root" variants.
This area map should facilitate tracking ongoing work through sub-issues regarding "virtual" event stream handlers.
Solution
In the Windows App Community SDK, there are seven possible "virtual" event stream handlers:
- Entity
- Connections
- LinkCollection
- ProjectRoleCollection
- PublisherRoleCollection
- UserRoleCollection
- AccentColor
Each "virtual" event stream handler is collectively used to implement the "root" event stream handlers, such as User, Project and Publisher.
The above should map 1:1 between the roaming models and the application models. Each "root" roaming model exist as a record, and the "virtual" roaming models are interfaced on these records.
In order to implement these "root" event stream handlers, we'll need finished implementations for the "virtual" variants.
This ticket serves to track and plan the implementation for these "root" event stream handlers.
Background
See #14
Problem
An area map for the various implemented event stream handlers is needed, with careful consideration for the differences between "virtual" and "root" variants.
This area map should facilitate tracking ongoing work through sub-issues regarding "virtual" event stream handlers.
Solution
In the Windows App Community SDK, there are seven possible "virtual" event stream handlers:
Each "virtual" event stream handler is collectively used to implement the "root" event stream handlers, such as User, Project and Publisher.
The above should map 1:1 between the roaming models and the application models. Each "root" roaming model exist as a record, and the "virtual" roaming models are interfaced on these records.
In order to implement these "root" event stream handlers, we'll need finished implementations for the "virtual" variants.
This ticket serves to track and plan the implementation for these "root" event stream handlers.