From cbf5e8954ac440d12144848e0ac7086b1af7327f Mon Sep 17 00:00:00 2001 From: Zlatin Balevsky Date: Wed, 4 Jul 2018 12:30:36 +0100 Subject: [PATCH] wip on design spec --- doc/design.md | 2 ++ 1 file changed, 2 insertions(+) diff --git a/doc/design.md b/doc/design.md index 9a9ae633..0f80c7d6 100644 --- a/doc/design.md +++ b/doc/design.md @@ -6,4 +6,6 @@ Initial bootstrap into the MuWire network is done in a similar fashion to Gnutel In response to the request, the HostCache sends back an I2P datagram containing b64 destinations of selected ultrapeers. The requesting client can then choose to close the I2P tunnel that it used to send the request because it will now know about ultrapeers to connect to. +### Connectivity to peers +Each node, be it leaf or ultrapeer will open two I2P tunnels - one for incoming I2P datagrams containing search results and incoming streaming connections for HTTP file transfer requests. In addition to this, ultrapeers will open an additional tunnel for incoming MuWire protocol connections. This simplifies implementation because the different pseudo-sockets can have dedicated logic to handle traffic, i.e. there is no need to multiplex between MuWire protocol connections and incoming HTTP requests.