e36c79f713
capitalize RpcError
2017-09-18 16:36:03 -04:00
9dde1a0bd4
rpc: comments
2017-08-25 17:57:09 -04:00
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
236489aecf
backlog must always have higher priority
2017-08-08 19:03:48 -04:00
797acbe911
ws: small comment
2017-08-08 17:33:17 -04:00
8267920749
[ws-client] write normal close message
2017-08-08 16:02:37 -04:00
23a87304cc
add a comment for PingPongLatencyTimer [ci skip]
2017-08-08 13:20:58 -04:00
57eee2466b
make WSClient thread-safe
2017-08-07 17:56:38 -04:00
5d66d1c28c
fixes from review
2017-08-05 13:11:00 -04:00
0013053fae
allow to change pong wait and ping period
2017-08-04 10:42:55 -04:00
1abbb11b44
do not exit from reconnectRoutine!
2017-08-03 22:44:18 -04:00
54903adeff
add IsReconnecting and IsActive methods
2017-08-03 19:10:15 -04:00
c08618f7e9
expose latency timer on WSClient
2017-08-03 19:10:14 -04:00
d578f7f81e
biff up WS client
...
What's new:
- auto reconnect
- ping/pong
- colored tests
2017-08-03 19:10:14 -04:00
b4ece65726
standardize key for errors (should be "err")
2017-06-14 12:50:49 +04:00
f803544195
new logging
2017-05-13 10:24:58 +02:00
6ba799132c
json.RawMessage in RPCRequest to defer parsing
2017-05-03 16:13:58 +02:00
efeadcc0f4
some cleanup from review
2017-04-28 23:18:38 -04:00
6c60c07f16
BROKEN: attempt to replace go-wire.JSON with json.Unmarshall in rpc
2017-04-28 16:24:06 +02:00
cc6dde96c1
rpc -> rpc/lib and rpc/tendermint -> rpc
2017-04-26 19:57:33 -04:00
Anton Kaliaev
Ethan Buchman
Ethan Frey