commit fc816fa692fac37bf322b336bfcb817b27b8da64
parent 53d8452733d86cd12d20ca17168f612251fa0e74
Author: Julius Bünger <buenger@mytum.de>
Date: Tue, 29 Oct 2024 14:51:25 +0100
cong: add more specifics to network generation id
Diffstat:
1 file changed, 7 insertions(+), 1 deletion(-)
diff --git a/developers/apis/cong.rst b/developers/apis/cong.rst
@@ -472,7 +472,13 @@ Once a peer id changes, all communication via open channels shall immediately
cease. To signal this, the mq is to be used.
To identify all queued messages that are to be cancelled, the 'network
generation id' is used. (This was decided to be implemented as a simple counter
-of 64 bit.)
+of 64 bit.) With each address and peer id change, the network generation id is
+incremented. When enqueueing a message with the mq, the current generation id
+is stored with is. This way, when the generation id changes, all enqueued
+messages with the old id (which still might refer to the old peer id in some
+way) can be identified and dequeued. It is important to manage the network
+generation id as close to the communicators as possible to be able to stop the
+actual outgoing messages as quick as possible.
..
64 bit: similar size to pid/hash
