Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Is a repo required to distribute updates on all model states? #301

Open
enikao opened this issue Aug 9, 2024 · 1 comment
Open

Is a repo required to distribute updates on all model states? #301

enikao opened this issue Aug 9, 2024 · 1 comment

Comments

@enikao
Copy link
Contributor

enikao commented Aug 9, 2024

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.

@enikao enikao added the delta label Aug 9, 2024
@enikao
Copy link
Contributor Author

enikao commented Aug 16, 2024

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant