1. 23 Dec, 2014 2 commits
    • Brian Tiger Chow's avatar
      refactor(bitswap) bitswap.Network now abstracts ipfs.Network + ipfs.Routing · 4ab8ad56
      Brian Tiger Chow authored
      @jbenet @whyrusleeping
      
      the next commit will change bitswap.Network.FindProviders to only deal
      with IDs
      4ab8ad56
    • 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 1 commit
  3. 08 Dec, 2014 2 commits
  4. 05 Dec, 2014 1 commit
  5. 28 Oct, 2014 1 commit
  6. 20 Oct, 2014 1 commit
  7. 07 Oct, 2014 1 commit
  8. 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
  9. 22 Sep, 2014 2 commits