- 08 Dec, 2014 1 commit
-
-
Brian Tiger Chow authored
for safety! use mockpeer.WithID methods to create peers in tests License: MIT Signed-off-by: Brian Tiger Chow <brian@perfmode.com>
-
- 07 Dec, 2014 3 commits
- 05 Dec, 2014 6 commits
-
-
Jeromy authored
-
Jeromy authored
-
Jeromy authored
-
Jeromy authored
-
Jeromy authored
-
Brian Tiger Chow authored
License: MIT Signed-off-by: Brian Tiger Chow <brian@perfmode.com>
-
- 28 Oct, 2014 2 commits
-
-
Brian Tiger Chow authored
to emphasize idempotence
-
Brian Tiger Chow authored
implementation will be patched to ensure bitswap messages cannot contain duplicate blocks or keys
-
- 25 Oct, 2014 2 commits
-
-
Brian Tiger Chow authored
-
Brian Tiger Chow authored
-
- 24 Oct, 2014 1 commit
-
-
Brian Tiger Chow authored
addresses concurrent access in bitswap session
-
- 20 Oct, 2014 1 commit
-
-
Juan Batiz-Benet authored
![](http://m.memegen.com/77n7dk.jpg)
-
- 07 Oct, 2014 1 commit
-
-
Jeromy authored
-
- 22 Sep, 2014 8 commits
-
-
Brian Tiger Chow authored
sending
-
Brian Tiger Chow authored
true -> always send to peer false -> use ledger-based strategy described in IPFS paper draft 3
-
Brian Tiger Chow authored
-
Brian Tiger Chow authored
-
Brian Tiger Chow authored
misc: * test network client getting more than max * test for find providers * rename factory method * local network * misc test improvements * test bitswap get block timeout * test provider exists but cannot connect to peer * test sending a message async over local network
-
Brian Tiger Chow authored
> Why expose num bytes sent and received? Makes it easy to test consistency of the ledgers > Got a better reason? Makes it possible to expose metrics to the people-facing API
-
Brian Tiger Chow authored
didn't run tests after the refactor. apologies.
-
Brian Tiger Chow authored
Move go-ipfs/bitswap package to go-ipfs/exchange/bitswap * Delineates the difference between the generic exchange interface and implementations (eg. BitSwap protocol) Thus, the bitswap protocol can be refined without having to overthink how future exchanges will work. Aspects common to BitSwap and other exchanges can be extracted out to the exchange package in piecemeal. Future exchange implementations can be placed in sibling packages next to exchange/bitswap. (eg. exchange/multilateral)
-