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

Question: Why are multiple dots necessary per element in an ORSWOT? #142

Open
widavies opened this issue Dec 19, 2023 · 0 comments
Open

Comments

@widavies
Copy link

I'm taking a look at the ORSWOT and trying to understand how it works. What doesn't quite make sense to me is this - why are multiple dots required for a single element? My first intuition was that you would only need to tag each element with a single dot for the most recent edit. If a element was a LWW register for example, when a concurrent edit is detected, we won't even bother appending each dot to the element (to have two). Instead, we'll just leave the dot present on each replica, but update the value to the more recent of the two changes. Then, the overarching version vector is updated to reflect that both replicas have merged in the other's change. In any case, I'm curious what I'm missing - why does each element need a dots() instead of just a dot() tagged against it and what goes wrong if only a single dot is used?

-type entries() :: dict(member(), dots()).

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

No branches or pull requests

1 participant