7 commits

Author	SHA1	Message	Date
Erik Johnston	313987187e	Fix tightloop over connecting to replication server ... If the client failed to process incoming commands during the initial set up of the replication connection it would immediately disconnect and reconnect, resulting in a tightloop. This can happen, for example, when subscribing to a stream that has a row that is too long in the backlog. The fix here is to not consider the connection successfully set up until the client has succesfully subscribed and caught up with the streams. This ensures that the retry logic timers aren't reset until then, meaning that if an error does happen during start up the client will continue backing off before retrying again.	2019-02-26 15:05:41 +00:00
Erik Johnston	62175a20e5	Docs	2019-02-19 11:38:40 +00:00
Erik Johnston	bc8fa1509d	Documentation	2019-02-19 11:24:59 +00:00
Erik Johnston	b4276a3896	Add a brief list of commands to docs	2017-03-31 11:34:45 +01:00
Erik Johnston	bfcf016714	Fix up docs	2017-03-31 11:19:24 +01:00
Erik Johnston	31e0fe9031	Fix indentation in docs/	2017-03-30 13:54:15 +01:00
Erik Johnston	7450693435	Initial TCP protocol implementation ... This defines the low level TCP replication protocol	2017-03-30 12:54:46 +01:00