Handle fetch when invited to a group on a server peer is already connected to #33

Closed
opened 2018-06-07 23:47:22 +00:00 by dan · 2 comments
Owner

When a peer connects to a server it automatically triggers a fetch to catch up.

However if a peer is connected to a server and then receives a new group invite, it will not fetch, and not catch up. This should be handled in one of two ways:

  1. Automatically, somewhere in processing an invite we should trigger a fetch if we detect a server connection

  2. expose the fetch api in cwtch peer and allow applications to decide

When a peer connects to a server it automatically triggers a fetch to catch up. However if a peer is connected to a server and then receives a new group invite, it will not fetch, and not catch up. This should be handled in one of two ways: 1) Automatically, somewhere in processing an invite we should trigger a fetch if we detect a server connection 2) expose the fetch api in cwtch peer and allow applications to decide
Owner

A 3rd possible approach here is to save undecryptable messages from a server for a given period of time and rerun them whenever there is a new group on a server

A 3rd possible approach here is to save undecryptable messages from a server for a given period of time and rerun them whenever there is a new group on a server
Author
Owner

semi handled: we do now reconnect and refetch. and these groups are now semi deprecated

semi handled: we do now reconnect and refetch. and these groups are now semi deprecated
dan closed this issue 2020-05-13 18:53:23 +00:00
Sign in to join this conversation.
No Assignees
2 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: cwtch.im/cwtch#33
No description provided.