-
-
Notifications
You must be signed in to change notification settings - Fork 1k
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
HTTP sync with multiple clients #6292
Comments
There are two checkpoints stored, a pull- and a push-checkpoint. |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed soon. Please update it or it may be closed to keep our repository organized. The best way is to add some more information or make a pull request with a test case. Also you might get help in fixing it at the RxDB Community Chat If you know you will continue working on this, just write any message to the issue (like "ping") to remove the stale tag. |
Hello, I need some clarification, how the HTTP sync described here could work with multiple clients.
Let suppose, we have 2 clients synced with remote db and go offline, then
0. initial state in all databases [{id: X, updateAt: 0}], the checkpoint would be (1, X).
The question is, how the document A finds its way to client 2? According to the server's pull logic from link above, updatedAt 2 > 1 is false, (updatedAt 2 == 1 && id A < Y) is also false. And so the document A will not be sent to the client 2.
The text was updated successfully, but these errors were encountered: