zolfa/tendermint - tendermint - Gitea: Git with a cup of tea

bft blockchain consensus consistency cryptocurrency cryptography db distributed-systems go

History

Anton Kaliaev 2fd8496bc1 correct handling of pings and pongs server: - always has read & write timeouts - ping handler never blocks the reader (see A) - sends regular pings to check up on a client A: at some point server write buffer can become full, so in order not to block reads from a client (see https://github.com/gorilla/websocket/issues/97), server may skip some pongs. As a result, client may disconnect. But you either have to do that or block the reader. There is no third way. client: - optional read & write timeouts - optional ping/pong to measure latency		7 years ago
..
id.go	Bare consensus refactor	9 years ago
node.go	correct handling of pings and pongs	7 years ago
node_test.go	new logging	8 years ago