2fd8496bc1
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 |
||
|---|---|---|
| .. | ||
| args_test.go | ||
| http_client.go | ||
| ws_client.go | ||
| ws_client_test.go | ||