1. 23 Dec, 2014 3 commits
    • Brian Tiger Chow's avatar
      Revert "bitswap: network interface changed" · 847826d9
      Brian Tiger Chow authored
      This reverts commit bf88f1aec5e3d397f97d64de52b52686cc7a8c8f.
      847826d9
    • Juan Batiz-Benet's avatar
      bitswap: network interface changed · c2186853
      Juan Batiz-Benet authored
      Had to change the network interface from DialPeer(peer.ID) to
      DialPeer(peer.PeerInfo), so that addresses of a provider are
      handed to the network.
      
      @maybebtc and I are discussing whether this should go all the
      way down to the network, or whether the network _should always
      work_ with just an ID (which means the network needs to be
      able to resolve ID -> Addresses, using the routing system.
      This latter point might mean that "routing" might need to
      break down into subcomponents. It's a bit sketchy that
      the Network would become smarter than just dial/listen and
      I/O, but maybe there's a distinction between net.Network,
      and something like a peernet.Network that has routing
      built in...)
      c2186853
    • Juan Batiz-Benet's avatar
      peer change: peer.Peer -> peer.ID · 42f61ec0
      Juan Batiz-Benet authored
      this is a major refactor of the entire codebase
      it changes the monolithic peer.Peer into using
      a peer.ID and a peer.Peerstore.
      
      Other changes:
      - removed handshake3.
      -	testutil vastly simplified peer
      -	secio bugfix + debugging logs
      -	testutil: RandKeyPair
      -	backpressure bugfix: w.o.w.
      -	peer: added hex enc/dec
      -	peer: added a PeerInfo struct
        PeerInfo is a small struct used to pass around a peer with
       	a set of addresses and keys. This is not meant to be a
       	complete view of the system, but rather to model updates to
       	the peerstore. It is used by things like the routing system.
      -	updated peer/queue + peerset
      -	latency metrics
      -	testutil: use crand for PeerID gen
       	RandPeerID generates random "valid" peer IDs. it does not
       	NEED to generate keys because it is as if we lost the key
       	right away. fine to read some randomness and hash it. to
       	generate proper keys and an ID, use:
       	  sk, pk, _ := testutil.RandKeyPair()
       	  id, _ := peer.IDFromPublicKey(pk)
       	Also added RandPeerIDFatal helper
      - removed old spipe
      - updated seccat
      - core: cleanup initIdentity
      - removed old getFromPeerList
      42f61ec0
  2. 13 Dec, 2014 2 commits
  3. 08 Dec, 2014 2 commits
  4. 05 Dec, 2014 1 commit
  5. 15 Nov, 2014 1 commit
  6. 05 Nov, 2014 1 commit
  7. 28 Oct, 2014 1 commit
  8. 20 Oct, 2014 1 commit
  9. 18 Oct, 2014 1 commit
    • Juan Batiz-Benet's avatar
      bitswap dials peers · 0ee59e4b
      Juan Batiz-Benet authored
      Important bugfix. Otherwise bitswap cannot message peers
      the node has not connected to yet :(
      0ee59e4b
  10. 07 Oct, 2014 1 commit
  11. 25 Sep, 2014 1 commit
    • Brian Tiger Chow's avatar
      feat(bitswap:network) propagate errors up the stack · 7b1cda70
      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.
      7b1cda70
  12. 23 Sep, 2014 3 commits
  13. 22 Sep, 2014 5 commits