tendermint

Commit Graph

Author	SHA1	Message	Date
Anton Kaliaev	2a24ae90c1	fixes from Jae's review 1. remove pointer 2. add Quit() method to Service interface	7 years ago
Anton Kaliaev	69b5da766c	service#Start, service#Stop signatures were changed See https://github.com/tendermint/tmlibs/issues/45	7 years ago
Zach Ramsay	d033470817	lil fixes	7 years ago
Zach Ramsay	d7cb291fb2	errcheck; sort some stuff out	7 years ago
Zach Ramsay	57ea4987f7	linting: apply errcheck part1	7 years ago
Ethan Buchman	a969e24177	crank context timeouts	7 years ago
Ethan Buchman	593c127257	rpc/lib/types: RPCResponse.Result is not a pointer	7 years ago
Emmanuel Odeke	6e5cd10399	rpc/lib/client: jitter test updates and only to-be run on releases * Updated code with feedback from @melekes, @ebuchman and @silasdavis. * Added Makefile clause `release` to only run the test on seeing tag `release` during releases i.e ```shell make release ``` which will run the comprehensive and long integration-ish tests.	7 years ago
Silas Davis	f6adddb4a8	Replace ResultsCh with ResponsesCh	7 years ago
Silas Davis	01be6fa309	Fix WSClient blocking in the readRoutine after Stop() as it tries to write to ResultsCh	7 years ago
Emmanuel Odeke	5504920ba3	rpc/lib/client: add jitter for exponential backoff of WSClient Fixes https://github.com/tendermint/tendermint/issues/751. Adds jitter to our exponential backoff to mitigate a self DDOS vector. The jitter is a randomly picked percentage of a second whose purpose is to ensure that each exponential backoff retry occurs within (1<<attempts) == 2*attempts, but with the delay each client will have a random buffer time before it tries to reconnect instead of all at once reconnections that might even bring back the previous conditions that might have caused the dial to the WSServer to have failed e.g Network outage * File descriptor exhaustion * False positives from firewalls etc	7 years ago
Anton Kaliaev	45ff7cdd0c	rewrite ws client to expose a callback instead of a channel callback gives more power to the publisher. plus it is optional comparing to a channel, which will block the whole client if you won't read from it.	7 years ago
Alexandre Thibault	ce36a0111a	rpc: subscribe on reconnection (#689 ) * rpc: subscribe on reconnection * rpc: fix unit tests	7 years ago
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	7 years ago
Anton Kaliaev	0013053fae	allow to change pong wait and ping period	7 years ago
Anton Kaliaev	d578f7f81e	biff up WS client What's new: - auto reconnect - ping/pong - colored tests	7 years ago

15 Commits (8e699c2bfdeed06a9994e6ca8568457789132a7c)