Planning and tracking implementation of "User" event stream handler

[Arlodotexe]

Background

See:

• Assessing and planning MVP event stream handler implementations #14
• Planning and tracking implementation of "Root" event stream handlers #16

Problem

An area map for the various implemented event stream handlers is needed.

This area map should facilitate tracking ongoing work through sub-issues regarding "virtual" event stream handlers.

The User roaming record needs to be implemented as read-only and modifiable virtual event stream handlers.

Solution

Implement the application model interfaces as event stream handlers, using User as the T in IDelegable<T> to represent the roaming data manipulated by the event stream handler.

Use the code introduced in #15 as a template for implementing both read-only and modifiable versions of this virtual event stream handler.

To summarize:

• Implement the application models:
  • IModifiableUser
    • IReadOnlyUser
    • IModifiableEntity
    • IModifiablePublisherRoleCollection
    • IModifiableProjectRoleCollection
  • IReadOnlyUser
    • IReadOnlyEntity
    • IReadOnlyPublisherRoleCollection
    • IReadOnlyProjectRoleCollection
• As event stream handlers controlling an instance of User
• Will collectively utilize the virtual event stream handlers to streamline implementation:
  • Planning and tracking implementation of "Entity" event stream handler #23
  • Planning and tracking implementation of "Publisher role collection" event stream handler #26
  • Planning and tracking implementation of "Project role collection" event stream handler #25