commit 2d91e825000361008875dd15e41e7597d6c9f70a parent e77a0e798c2a63ba6ccf7756eb294be54bfbb553 Author: Jacki <jacki@thejackimonster.de> Date: Mon, 26 Feb 2024 16:33:10 +0100 cong: correct potential effects on messenger service Signed-off-by: Jacki <jacki@thejackimonster.de> Diffstat:
| M | developers/apis/cong.rst | | | 9 | +++++++-- |
1 file changed, 7 insertions(+), 2 deletions(-)
diff --git a/developers/apis/cong.rst b/developers/apis/cong.rst @@ -97,8 +97,13 @@ TODO lookup rst lists! This is not significantly affected by a reconnect as it only looks up peer and port in the DHT, so in the meanwhile it's looking for other peers. TODO this is very unclear to me! - - Messenging: This is not affected too badly - for a reconnection with this - service GNS lookups are required. + - Messenger: All CADET connections would break and the peer might assume that + all previously connected peers went offline. So it would require a + mechanism to reconnect to peers with a known peer identity which offer + routing capability (open port via CADET to connect to). In case the peer + itself is providing such capability, it would help to know about peer ID + changes ahead of time to communicate a switch between IDs to other peers. + For other reconnections via GNS lookups are required. - Conversation: The call would be interrupted until the new peer id of the other has been found via GNS.