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
Is a compatible repository required to keep a history of all commands clients sent?
This can be helpful (probably even necessary) for live collaboration.
The difference to #294 is in what we mean with "history": Here, we talk about all changes that happened to the model.
In principle, we could recreate the current state of the model by executing all these changes in order, from the very beginning. There is only one linear set of applied commands, even though they might cancel each other out, e.g. if we first created a node, and deleted it again later.
Option A: Repo must keep a history of commands
Pro:
Reliable source for live collaboration
Con:
Might need a lot of storage
Would only make sense if we had an API to access previous states in that history
Option B: Repo can chose to keep a history of commands, but doesn't need to
Do we distinguish between commands that can never be correct or only the current state?
Example: change a property of a node
a) that node never existed
b) that node has been deleted
==> No, cannot without keeping a history
enikao
changed the title
Repository does not need to keep a history of commands
Repository does not need to keep a history (of commands)
Aug 2, 2024
Is a compatible repository required to keep a history of all commands clients sent?
This can be helpful (probably even necessary) for live collaboration.
The difference to #294 is in what we mean with "history": Here, we talk about all changes that happened to the model.
In principle, we could recreate the current state of the model by executing all these changes in order, from the very beginning. There is only one linear set of applied commands, even though they might cancel each other out, e.g. if we first created a node, and deleted it again later.
Option A: Repo must keep a history of commands
Pro:
Con:
Option B: Repo can chose to keep a history of commands, but doesn't need to
Pro:
Con:
Option C: Repo should not keep a history of commands
Pro:
Con:
Decision: Option B
Option A might be too resource hungry, option C cannot be enforced. B is a good compromise.
We accept the increased variability.
The text was updated successfully, but these errors were encountered: