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.
 
 
 
 
 
 
Ethan Buchman dab31d0166 version bump to 0.4.0 8 years ago
upnp initial commit 9 years ago
.gitignore version bump to 0.4.0 8 years ago
LICENSE Change license to Apache2.0 9 years ago
README.md circle badge 9 years ago
addrbook.go QuitService->BaseService 8 years ago
addrbook_test.go dial seeds error handling 8 years ago
config.go configurable fuzz conn 9 years ago
connection.go use go-flowrate instead of flowcontrol 8 years ago
fuzz.go configurable fuzz conn 9 years ago
ip_range_counter.go Add RemoteAddr and ListenAddr to NodeInfo; Refactor IPRange logic 9 years ago
listener.go dial seeds error handling 8 years ago
listener_test.go MakeConnectedSwitches function 9 years ago
log.go initial commit 9 years ago
netaddress.go some dial seeds fixes 8 years ago
peer.go No global config 9 years ago
peer_set.go Add RemoteAddr and ListenAddr to NodeInfo; Refactor IPRange logic 9 years ago
peer_set_test.go Add RemoteAddr and ListenAddr to NodeInfo; Refactor IPRange logic 9 years ago
pex_reactor.go version bump to 0.4.0 8 years ago
secret_connection.go Confirm to go-wire new TypeByte behavior 9 years ago
secret_connection_test.go initial commit 9 years ago
switch.go some dial seeds fixes 8 years ago
switch_test.go some dial seeds fixes 8 years ago
types.go close conns on filter; fix order in MakeConnectedSwitch 8 years ago
util.go initial commit 9 years ago
version.go version bump to 0.4.0 8 years ago

README.md

tendermint/go-p2p

CircleCI

tendermint/go-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(addrBookFilePath)
pexReactor := p2p.NewPEXReactor(book)
...
switch := NewSwitch([]Reactor{pexReactor, myReactor, ...})