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

2017-08-10 17:53:49 -04:00

..

id.go

Bare consensus refactor

2015-11-01 11:34:08 -08:00

node_test.go

new logging

2017-05-13 10:24:58 +02:00

node.go

correct handling of pings and pongs

2017-08-10 17:53:49 -04:00