From 2958ce76c6b4de6768a1d628177333c0fb00f761 Mon Sep 17 00:00:00 2001 From: Devon Hudson Date: Wed, 11 Jan 2023 11:11:52 -0700 Subject: [PATCH] Fix s&f architecture docs typo --- cmd/dendrite-demo-pinecone/ARCHITECTURE.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/cmd/dendrite-demo-pinecone/ARCHITECTURE.md b/cmd/dendrite-demo-pinecone/ARCHITECTURE.md index 76649db4c..0eb06a881 100644 --- a/cmd/dendrite-demo-pinecone/ARCHITECTURE.md +++ b/cmd/dendrite-demo-pinecone/ARCHITECTURE.md @@ -44,7 +44,7 @@ In the future this will probably need to change in order to handle more complex - If sending to any of the relay servers succeeds, that transaction is considered to be successfully sent. - 2: The relay server `forwarder` stores the transaction json in it's database and marks it as destined for `P2P Node B`. - 3: When `P2P Node B` comes online, it queries all it's relay servers for any missed messages. -- 4: The relay server `retriever` will look in it's database for any transactions that are destined for `P2P Node B` and return them one at a time. +- 4: The relay server `retriever` will look in it's database for any transactions that are destined for `P2P Node B` and returns them one at a time. For now, it is important that we don’t design out a hybrid approach of having both sender-side and recipient-side relay servers. Both approaches make sense and determining which makes for a better experience depends on the use case.