You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
 
 
 
 
 
 
Jae Kwon fa956596dc Merge remote-tracking branch 'origin/config' into develop 9 years ago
..
upnp BaseService and BaseReactor refactor and unification 9 years ago
README.md Blockpool better timeouts, download rate observation, quicker switching to consensus; Id -> ID (sorry, this doesn't belong here) 9 years ago
addrbook.go Use rpc/client/ws_client; OnStart() returns error 9 years ago
addrbook_test.go addrbook cleanup 10 years ago
config.go RPCResponse.Result && EventData are registered interfaces; -skip_upnp option 9 years ago
connection.go blockchain parameter && log tweaks 9 years ago
listener.go RPCResponse.Result && EventData are registered interfaces; -skip_upnp option 9 years ago
log.go Package import path change 10 years ago
netaddress.go more config options 9 years ago
peer.go mempool tests 9 years ago
peer_set.go UUID -> PubKeyEd25519 9 years ago
peer_set_test.go various bug fixes 9 years ago
pex_reactor.go Blockpool better timeouts, download rate observation, quicker switching to consensus; Id -> ID (sorry, this doesn't belong here) 9 years ago
secret_connection.go tendermint/binary -> tendermint/wire 9 years ago
secret_connection_test.go crypto byte arrays are fixed length 9 years ago
switch.go precommit nil if locked and no POL 9 years ago
switch_test.go more versioning 9 years ago
util.go cleanup 10 years ago
version.go more versioning 9 years ago

README.md

tendermint/p2p

tendermint/p2p provides an abstraction around peer-to-peer communication.

Peer/MConnection/Channel

Each peer has one MConnection (multiplex connection) instance.

multiplex noun a system or signal involving simultaneous transmission of several messages along a single channel of communication.

Each MConnection handles message transmission on multiple abstract communication Channels. Each channel has a globally unique byte id. The byte id and the relative priorities of each Channel are configured upon initialization of the connection.

There are two methods for sending messages:

func (m MConnection) Send(chID byte, msg interface{}) bool {}
func (m MConnection) TrySend(chID byte, msg interface{}) bool {}

Send(chID, msg) is a blocking call that waits until msg is successfully queued for the channel with the given id byte chID. The message msg is serialized using the tendermint/wire submodule's WriteBinary() reflection routine.

TrySend(chID, msg) is a nonblocking call that returns false if the channel's queue is full.

Send() and TrySend() are also exposed for each Peer.

Switch/Reactor

The Switch handles peer connections and exposes an API to receive incoming messages on Reactors. Each Reactor is responsible for handling incoming messages of one or more Channels. So while sending outgoing messages is typically performed on the peer, incoming messages are received on the reactor.

// Declare a MyReactor reactor that handles messages on MyChannelID.
type MyReactor struct{}

func (reactor MyReactor) GetChannels() []*ChannelDescriptor {
    return []*ChannelDescriptor{ChannelDescriptor{ID:MyChannelID, Priority: 1}}
}

func (reactor MyReactor) Receive(chID byte, peer *Peer, msgBytes []byte) {
    r, n, err := bytes.NewBuffer(msgBytes), new(int64), new(error)
    msgString := ReadString(r, n, err)
    fmt.Println(msgString)
}

// Other Reactor methods omitted for brevity
...

switch := NewSwitch([]Reactor{MyReactor{}})

...

// Send a random message to all outbound connections
for _, peer := range switch.Peers().List() {
    if peer.IsOutbound() {
        peer.Send(MyChannelID, "Here's a random message")
    }
}

PexReactor/AddrBook

A PEXReactor reactor implementation is provided to automate peer discovery.

book := p2p.NewAddrBook(config.App.GetString("AddrBookFile"))
pexReactor := p2p.NewPEXReactor(book)
...
switch := NewSwitch([]Reactor{pexReactor, myReactor, ...})