Details
-
Improvement
-
Status: Open
-
Major
-
Resolution: Unresolved
-
None
-
None
-
None
Description
The state of the model-user interaction is kept in the EventStore. The ES logs all request/response pairs (LogEntry) and for each holds 1:n relations to Aggregtators.
An Aggegator may be related to many LogEntries (resulting in m:n in total) and acts as a facade to the DisplayModel. DM's are rendered by views (RoDisplay). Incoming updates refresh the views.
For kroviz the scenario you described boils down to: an updated entity may be part of an additional object list as well (and it's Aggregator/RoDisplay pair).
There needs to be an (additional) relation between certain LogEntries and/or their Aggregators to handle this .
Attachments
Issue Links
- is cloned by
-
CAUSEWAY-2837 [kroviz] Execute Integration Tests against Docker Image (Demo)
- Open