23096de3c4
fix(net) pass contexts to dial peer
2014-11-05 10:04:20 -08:00
c60d011764
fix(exchange) add context to DialPeer
2014-11-05 10:04:20 -08:00
d92db12460
lots of logging
2014-10-26 00:45:40 +00:00
ab7491f809
logging, logging, and some minor logging
2014-10-25 14:50:22 -07:00
9ca87fbb93
peer.Peer is now an interface
...
2014-10-20 03:26:46 -07:00
a5a7d99860
meant to call net.DialPeer
2014-10-18 04:28:24 -07:00
1555ce7c48
bitswap dials peers
...
Important bugfix. Otherwise bitswap cannot message peers
the node has not connected to yet :(
2014-10-18 04:28:23 -07:00
338b037238
clean up and add inet.Network to bitswap
...
new Service interface
2014-10-10 20:43:04 -07:00
e2a9c5de00
feat(net:service, routing) remove error return value
2014-09-24 23:35:36 -04:00
0e494690b3
feat(bitswap:network) propagate errors up the stack
...
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.
2014-09-24 23:35:36 -04:00
0c67019447
style(exch:bitswap) rename adapter, session, etc.
...
style(exch:bitswap) rename NetMessage adapter impl
2014-09-22 04:06:14 -07:00
