- 24 Dec, 2014 1 commit
-
-
Juan Batiz-Benet authored
-
- 23 Dec, 2014 5 commits
-
-
Juan Batiz-Benet authored
-
Juan Batiz-Benet authored
Connectedness was totally incorrect. added a test case.
-
Juan Batiz-Benet authored
-
Juan Batiz-Benet authored
- Make sure we call IdentifyConn on dialed out conns - we wait until the identify is **done** before return - on listening case, we can also wait. - tests now make sure dial does wait. - tests now make sure we can wait on listening case.
-
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
-
- 18 Dec, 2014 3 commits
-
-
Juan Batiz-Benet authored
-
Juan Batiz-Benet authored
-
Juan Batiz-Benet authored
-
- 16 Dec, 2014 6 commits
-
-
Juan Batiz-Benet authored
-
Juan Batiz-Benet authored
-
Juan Batiz-Benet authored
-
Juan Batiz-Benet authored
-
Brian Tiger Chow authored
-
Juan Batiz-Benet authored
-
- 09 Dec, 2014 2 commits
-
-
Juan Batiz-Benet authored
-
Juan Batiz-Benet authored
-
- 08 Dec, 2014 1 commit
-
-
Brian Tiger Chow authored
having an error return value makes the interface a bit confusing to use. Just ponder... What would an error returned from a predicate function mean? License: MIT Signed-off-by: Brian Tiger Chow <brian@perfmode.com>
-
- 05 Dec, 2014 1 commit
-
-
Jeromy authored
-
- 18 Nov, 2014 1 commit
-
-
Juan Batiz-Benet authored
-
- 09 Nov, 2014 1 commit
-
-
Jeromy authored
-
- 05 Nov, 2014 4 commits
-
-
Brian Tiger Chow authored
@jbenet
-
Brian Tiger Chow authored
-
Brian Tiger Chow authored
-
Juan Batiz-Benet authored
-
- 26 Oct, 2014 2 commits
-
-
Juan Batiz-Benet authored
-
Juan Batiz-Benet authored
-
- 20 Oct, 2014 1 commit
-
-
Juan Batiz-Benet authored
![](http://m.memegen.com/77n7dk.jpg)
-
- 18 Oct, 2014 1 commit
-
-
Jeromy authored
-
- 10 Oct, 2014 2 commits
- 26 Sep, 2014 1 commit
-
-
Juan Batiz-Benet authored
-
- 22 Sep, 2014 5 commits
-
-
Juan Batiz-Benet authored
-
Juan Batiz-Benet authored
-
Brian Tiger Chow authored
-
Juan Batiz-Benet authored
-
Juan Batiz-Benet authored
-