mirror of
https://github.com/ipfs/kubo.git
synced 2026-02-23 19:37:46 +08:00
b84fa2b493
We had a very nasty problem: handshakes were serial so incoming dials would wait for each other to finish handshaking. this was particularly problematic when handshakes hung-- nodes would not recover quickly. This led to gateways not bootstrapping peers fast enough. The approach taken here is to do what crypto/tls does: defer the handshake until Read/Write[1]. There are a number of reasons why this is _the right thing to do_: - it delays handshaking until it is known to be necessary (doing io) - it "accepts" before the handshake, getting the handshake out of the critical path entirely. - it defers to the user's parallelization of conn handling. users must implement this in some way already so use that, instead of picking constants surely to be wrong (how many handshakes to run in parallel?) [0] http://golang.org/src/crypto/tls/conn.go#L886 |
||
|---|---|---|
| .. | ||
| conn | ||
| mock | ||
| swarm | ||
| interface.go | ||
| README.md | ||
Network
The IPFS Network package handles all of the peer-to-peer networking. It connects to other hosts, it encrypts communications, it muxes messages between the network's client services and target hosts. It has multiple subcomponents:
Conn- a connection to a single PeerMultiConn- a set of connections to a single PeerSecureConn- an encrypted (tls-like) connection
Swarm- holds connections to Peers, multiplexes from/to eachMultiConnMuxer- multiplexes betweenServicesandSwarm. HandlesRequet/Reply.Service- connects between an outside client service and Network.Handler- the client service part that handles requests
It looks a bit like this:
