tendermint

291 MiB

Tree: cc2b418f7f

Author	SHA1	Message	Date
Ethan Buchman	9dde1a0bd4	rpc: comments	7 years ago
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
Anton Kaliaev	236489aecf	backlog must always have higher priority	7 years ago
Anton Kaliaev	5d66d1c28c	fixes from review	8 years ago
Anton Kaliaev	0013053fae	allow to change pong wait and ping period	8 years ago
Anton Kaliaev	d578f7f81e	biff up WS client What's new: - auto reconnect - ping/pong - colored tests	8 years ago