Commits · 13ab516c1c4ad7390dafe454b645338d0bd4fe30 · dms3 / go-bitswap

07 Dec, 2014 1 commit
- prevent sending of same block to a peer twice · 13ab516c
  Jeromy authored Dec 07, 2014
  
  13ab516c
05 Dec, 2014 2 commits
- randomize rebroadcast target · 6ee1fe5e
  Jeromy authored Nov 20, 2014
  
  6ee1fe5e
- move some variables into strategy · c6af3fe4
  Jeromy authored Nov 19, 2014
  
  c6af3fe4
20 Oct, 2014 1 commit
- peer.Peer is now an interface · 3ef5ef2e
  Juan Batiz-Benet authored Oct 20, 2014
```
![](http://m.memegen.com/77n7dk.jpg)
```
  3ef5ef2e
22 Sep, 2014 4 commits

refac(bitswap, util) extract KeySet · 1afac8dc
Brian Tiger Chow authored Sep 21, 2014

1afac8dc
docs(bitswap:strat) interface comments · e040a00a
Brian Tiger Chow authored Sep 19, 2014

e040a00a

test(exch:bs:strategy) test accounting consistency · d2ea3d25

Brian Tiger Chow authored Sep 18, 2014

> 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

d2ea3d25

refac(exchange) bitswap -> exchange/bitswap · 7cb2f524

Brian Tiger Chow authored Sep 18, 2014

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)

7cb2f524