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

Logout problems #36

Open
ekuiter opened this issue Jun 11, 2019 · 0 comments
Open

Logout problems #36

ekuiter opened this issue Jun 11, 2019 · 0 comments

Comments

@ekuiter
Copy link
Owner

ekuiter commented Jun 11, 2019

When the WebSocket is closed, the collaborator is not "leaved" from its collaborative sessions. This is intended, so that the collaborator may go online again. However, if the collaborator never goes online again, synchronization is impossible when resolving conflicts.

So, we should implement a timout / an "inactive" collaborator concept to avoid that. Or just leave all collaborative sessions on WebSocket close, but let the collaborator instance live (then offline editing is impossible, but at least we can sign in again as the same collaborator).

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