You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Repo recieves "change property x to 1", then "change property x to 2".
Repo is designed to send update events only every 5 seconds. Does it HAVE to send both updates, or can it choose to consolidate it to one "change property x to 2" event?
Repo might also decide to "undo" a previous change as result of conflict resolution. "Undo" is a regular event, but related to a previous event.
The text was updated successfully, but these errors were encountered:
Repository MUST distribute state changes (aka events) to represent all model states.
It is up to repository to decide how many / how long commands it merges into one state change.
In other words: Whatever is materialized in the repo has to be distributed; the repo can decide at which intervals it materializes.
Repo recieves "change property x to 1", then "change property x to 2".
Repo is designed to send update events only every 5 seconds. Does it HAVE to send both updates, or can it choose to consolidate it to one "change property x to 2" event?
Repo might also decide to "undo" a previous change as result of conflict resolution. "Undo" is a regular event, but related to a previous event.
The text was updated successfully, but these errors were encountered: