From dbd6cd689eb49d5a5bc40b3d8796114945f48cee Mon Sep 17 00:00:00 2001 From: Simon Ser Date: Fri, 17 Apr 2020 18:29:49 +0200 Subject: [PATCH] doc/architecture: ring buffers are now per-channel --- doc/architecture.md | 10 +++++----- 1 file changed, 5 insertions(+), 5 deletions(-) diff --git a/doc/architecture.md b/doc/architecture.md index 7eccccf..7a1bed1 100644 --- a/doc/architecture.md +++ b/doc/architecture.md @@ -12,11 +12,11 @@ and try to open an upstream connection for each network. ## Ring buffer In order to correctly send history to each downstream client, soju maintains -for each network a single-producer multiple-consumer ring buffer. The network's -upstream connection produces messages and multiple downstream connections -consume these messages. Each downstream client may have a different cursor in -the history: for instance a client may be 10 messages late while another has -consumed all pending messages. +for each upstream channel a single-producer multiple-consumer ring buffer. The +network's upstream connection produces messages and multiple downstream +connections consume these messages. Each downstream client may have a different +cursor in the history: for instance a client may be 10 messages late while +another has consumed all pending messages. ## Goroutines