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

Operations should be queued in case of reconnection? #87

Open
laggingreflex opened this issue Feb 22, 2017 · 1 comment
Open

Operations should be queued in case of reconnection? #87

laggingreflex opened this issue Feb 22, 2017 · 1 comment

Comments

@laggingreflex
Copy link
Contributor

Even after #86 the file changes that were lost due to lost connection still aren't synced. A queue could help ensuring the file changes are synced in this case

@joelgriffith
Copy link
Contributor

A queue makes sense, though most consumers (including myself) rely on bigSync to sort of "catch-up" any out-of-sync changes.

A queue could potentially be a lot of work

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

2 participants