- 25 Oct, 2014 1 commit
-
-
Jeromy authored
-
- 20 Oct, 2014 1 commit
-
-
Juan Batiz-Benet authored
![](http://m.memegen.com/77n7dk.jpg)
-
- 18 Oct, 2014 2 commits
-
-
Juan Batiz-Benet authored
-
Juan Batiz-Benet authored
Important bugfix. Otherwise bitswap cannot message peers the node has not connected to yet :(
-
- 11 Oct, 2014 1 commit
-
-
Juan Batiz-Benet authored
new Service interface
-
- 25 Sep, 2014 2 commits
-
-
Brian Tiger Chow authored
-
Brian Tiger Chow authored
Rather than pushing errors back down to lower layers, propagate the errors upward. This commit adds a `ReceiveError` method to BitSwap's network receiver. Still TODO: rm the error return value from: net.service.handler.HandleMessage This is inspired by delegation patterns in found in the wild.
-
- 22 Sep, 2014 2 commits
-
-
Brian Tiger Chow authored
style(exch:bitswap) rename NetMessage adapter impl
-
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)
-