- 10 Jun, 2020 3 commits
-
-
Dirk McCormick authored
-
Dirk McCormick authored
-
Dirk McCormick authored
-
- 02 Jun, 2020 1 commit
-
-
dirkmc authored
* feat: total wants gauge * fix: in gauges count wants regardless of which peers they're sent to * fix: want block gauge calculation * refactor: simplify peermanagerwants
-
- 21 May, 2020 1 commit
-
-
Steven Allen authored
Instead of tracking offsets, just create a "new" slice starting with the broadcast cancel slice. Under the covers, this will just use the same memory over and over.
-
- 20 May, 2020 1 commit
-
-
Dirk McCormick authored
-
- 19 May, 2020 1 commit
-
-
Dirk McCormick authored
-
- 22 Apr, 2020 1 commit
-
-
Steven Allen authored
* feat: small optimizations * feat: move broadcast wantlist into the peermanager This deduplicates some state and allows us to do less book-keeping for broadcast wants. We should probably rename the PeerManager to the WantManager and rename the WantManager to something else. * fix: lint warnings
-
- 21 Apr, 2020 1 commit
-
-
dirkmc authored
* refactor: add reverse index to peerWantManager to speed up cancels * refactor: in peerWantManager use ForEach instead of allocating lists
-
- 03 Apr, 2020 1 commit
-
-
Dirk McCormick authored
-
- 24 Mar, 2020 2 commits
-
-
Dirk McCormick authored
-
Steven Allen authored
This makes it easier to tell where module boundaries are.
-
- 16 Mar, 2020 1 commit
-
-
Steven Allen authored
And expose a separate function for _just_ getting want-blocks. When the user runs `ipfs bitswap wantlist`, they expect to see everything the node is currently looking for. Co-Authored-By: dirkmc <dirkmdev@gmail.com>
-
- 13 Mar, 2020 1 commit
-
-
Dirk McCormick authored
-
- 30 Jan, 2020 2 commits
-
-
Steven Allen authored
This makes reading the docs much easier as it's clear what's "private" and what's not. fixes #238
-
dirkmc authored
This commit extends the bitswap protocol with two additional wantlist properties: * WANT_HAVE/HAVE: Instead of asking for a block, a node can specify that they want to know if any peers "have" the block. * WANT_HAVE_NOT/HAVE_NOT: Instead of waiting for a timeout, a node can explicitly request to be told immediately if their peers don't currently have the given block. Additionally, nodes now tell their peers how much data they have queued to send them when sending messages. This allows peers to better distribute requests, keeping all peers busy but not overloaded. Changes in this PR are described in: https://github.com/ipfs/go-bitswap/issues/186
-