tendermint/p2p
Jae Kwon 61d1635085 Fixed tests 2014-12-21 21:47:38 -08:00
..
upnp made cmd/, removed crypto/ 2014-11-07 23:27:03 -08:00
README.md fixed algorithm 2014-10-03 01:09:26 -07:00
addrbook.go Begin writing RPC HTTP Server 2014-12-16 05:43:23 -08:00
addrbook_test.go addrbook cleanup 2014-07-10 02:19:50 -07:00
connection.go Fixed tests 2014-12-21 21:47:38 -08:00
listener.go Fixed tests 2014-12-21 21:47:38 -08:00
log.go Refactor Tx, Validator, and Account structure 2014-12-16 05:45:40 -08:00
netaddress.go Refactor Tx, Validator, and Account structure 2014-12-16 05:45:40 -08:00
peer.go Refactor Tx, Validator, and Account structure 2014-12-16 05:45:40 -08:00
peer_set.go implementing block_manager. currently only supports one datatype. 2014-07-29 23:53:35 -07:00
pex_reactor.go Refactor Tx, Validator, and Account structure 2014-12-16 05:45:40 -08:00
switch.go Refactor Tx, Validator, and Account structure 2014-12-16 05:45:40 -08:00
switch_test.go Refactor Tx, Validator, and Account structure 2014-12-16 05:45:40 -08:00
util.go cleanup 2014-07-09 14:27:32 -07:00

README.md

P2P Module

P2P provides an abstraction around peer-to-peer communication.
Communication happens via Reactors that react to messages from peers.
Each Reactor has one or more Channels of communication for each Peer.
Channels are multiplexed automatically and can be configured.
A Switch is started upon app start, and handles Peer management.
A PEXReactor implementation is provided to automate peer discovery.

Channels

Each peer connection is multiplexed into channels. The p2p module comes with a channel implementation used for peer discovery (called PEX, short for "peer exchange").

Channel "PEX"
Messages
  • pexRequestMsg
  • pexResponseMsg

Resources