Automatic reconnection

[mmacfadden]

When the client gets disconnected, it should try to reconnect. While disconnected the various API functions should continue to work as reasonably expected, assuming the instance of the client remains in memory:

Models

• The model API should not detach the model, and should cue local changes. When the client reconnects the model should resynchronize with the server, and the user can then continue editing while online again.
• When disconnected all remote collaborators should appear to leave the model. When reconnecting the current remote collaborators will appear to open the model.
• When disconnected remote references will be removed. Local references will still work. Upon reconnection, current references at the server will be re-added. Local references will be re-shared to the server.
• It will not be possible to create or delete models while offline.
• If a user looses permissions to a model, when the client reconnects, the mode will be closed.
• If a model is deleted while the client is disconnected, when the client reconnects, the mode will be closed.

Activities

• Any currently joined activities will remained joined, but all remote participants will leave.
• Upon reconnection all joined activities will rejoin.
• Activities can be joined offline, and will be joined when reconnected.
  Presence
• When disconnected user presence will appear to go offline.
• Upon reconnection all presence subscriptions will be re-subscribed.

Chat

• Joined chat rooms will be re-joined when reconnected.
• It will not be possible to send messages, or to join / leave chat's while offline.

Identity

• Cached identities can be looked up, others will return undefined.