Ethan Frey 57527f9f67 | 8 years ago | |
---|---|---|
.. | ||
upnp | 8 years ago | |
CHANGELOG.md | 8 years ago | |
Dockerfile | 8 years ago | |
README.md | 8 years ago | |
addrbook.go | 8 years ago | |
addrbook_test.go | 8 years ago | |
connection.go | 8 years ago | |
connection_test.go | 8 years ago | |
fuzz.go | 8 years ago | |
ip_range_counter.go | 8 years ago | |
listener.go | 8 years ago | |
listener_test.go | 8 years ago | |
log.go | 8 years ago | |
netaddress.go | 8 years ago | |
netaddress_test.go | 8 years ago | |
peer.go | 8 years ago | |
peer_set.go | 8 years ago | |
peer_set_test.go | 8 years ago | |
peer_test.go | 8 years ago | |
pex_reactor.go | 8 years ago | |
pex_reactor_test.go | 8 years ago | |
secret_connection.go | 8 years ago | |
secret_connection_test.go | 8 years ago | |
switch.go | 8 years ago | |
switch_test.go | 8 years ago | |
types.go | 8 years ago | |
util.go | 8 years ago | |
version.go | 8 years ago |
tendermint/tendermint/p2p
tendermint/tendermint/p2p
provides an abstraction around peer-to-peer communication.
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
Channel
s. 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
.
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")
}
}
A PEXReactor
reactor implementation is provided to automate peer discovery.
book := p2p.NewAddrBook(addrBookFilePath)
pexReactor := p2p.NewPEXReactor(book)
...
switch := NewSwitch([]Reactor{pexReactor, myReactor, ...})