You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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).
The text was updated successfully, but these errors were encountered:
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).
The text was updated successfully, but these errors were encountered: