Brian Tiger Chow
86c438b6e1
refactor() message API
...
performing CR in the form of a PR. Let me know what you think.
License: MIT
Signed-off-by: Brian Tiger Chow <brian@perfmode.com>
2014-12-17 23:44:41 -08:00
Jeromy
5b6a5e807f
implement bitswap roundWorker
...
make vendor
2014-12-17 23:44:39 -08:00
Juan Batiz-Benet
41751b4938
Integrated new network into ipfs
2014-12-16 14:47:29 -08:00
Brian Tiger Chow
74eb03231d
fix(core, peer) helpers to testutil, err handling
...
License: MIT
Signed-off-by: Brian Tiger Chow <brian@perfmode.com>
2014-12-08 14:32:52 -08:00
Brian Tiger Chow
d77c4bb5e0
refactor(peer): create peer through peerstore
...
for safety!
use mockpeer.WithID methods to create peers in tests
License: MIT
Signed-off-by: Brian Tiger Chow <brian@perfmode.com>
2014-12-08 02:10:42 -08:00
Jeromy
d53deebada
wire GetBlocks into blockservice
2014-12-05 20:53:26 +00:00
Brian Tiger Chow
91a31a3e7d
test(bitswap/message) no duplicates
2014-10-27 21:58:21 -07:00
Brian Tiger Chow
cebeff43b9
style(bitswap/message) rename method -> AddBlock
...
to emphasize idempotence
2014-10-27 21:58:21 -07:00
Brian Tiger Chow
842b910853
style(bitswap/message) rename AppendWanted -> AddWanted
...
implementation will be patched to ensure bitswap messages cannot contain
duplicate blocks or keys
2014-10-27 21:58:20 -07:00
Brian Tiger Chow
80b573425b
refactor(bitswap) mv proto PBMessage -> Message
2014-10-22 21:49:46 -07:00
Brian Tiger Chow
15605fb18f
refactor(exchange/bitswap) move proto to internal pb package
2014-10-22 15:54:17 -07:00
Juan Batiz-Benet
9ca87fbb93
peer.Peer is now an interface
...
2014-10-20 03:26:46 -07:00
Jeromy
6e0cfb3273
removed error from return type of blocks.NewBlock()
2014-10-07 20:46:01 +00:00
Brian Tiger Chow
315e121ef9
feat(bitswap:message) implement FromNet
2014-09-22 04:06:16 -07:00
Brian Tiger Chow
800af9ca3a
fix(bitswap:message) don't use proto internally
2014-09-22 04:06:15 -07:00
Brian Tiger Chow
fd086b9c48
refac(exchange) bitswap -> exchange/bitswap
...
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)
2014-09-22 04:06:13 -07:00
