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

Client Synchronization: Ensure multiple same synchronizations don't crash #92

Open
Zhiyuan-Amos opened this issue Oct 29, 2021 · 0 comments

Comments

@Zhiyuan-Amos
Copy link
Owner

Zhiyuan-Amos commented Oct 29, 2021

If synchronization occurs multiple times, then the same data will be CUD. This can lead to errors if not handled well. Let's:

  1. Add conditional logic to ignore C & D if the entry already exists or does not exist respectively.
  2. Update only if the incoming data is newer (assuming Client DateTime are synchronized)

To prevent race conditions with local CUD. local CUD should be disallowed when synchronization is running.

@Zhiyuan-Amos Zhiyuan-Amos changed the title Synchronization: Ensure multiple same synchronizations don't crash Client Synchronization: Ensure multiple same synchronizations don't crash Dec 5, 2021
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