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

Track "source" for PatchSet #295

Open
LPGhatguy opened this issue Feb 19, 2020 · 0 comments · May be fixed by #699
Open

Track "source" for PatchSet #295

LPGhatguy opened this issue Feb 19, 2020 · 0 comments · May be fixed by #699
Labels
two-way-sync This will help further two-way-sync.

Comments

@LPGhatguy
Copy link
Contributor

To prevent changes ping-ponging between clients, patch sets should have a source field attached to them. Each endpoint, including servers and clients, should generate a GUID source for themselves so that they can ignore changes that come from their own changes.

In tandem with #293, we should be able to track change sources for two-way sync and prevent clients from getting into funny states with themselves at least.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
two-way-sync This will help further two-way-sync.
Projects
None yet
1 participant