From a11e0c5ff9f47da89e763cfe46a9bcd6f02b5098 Mon Sep 17 00:00:00 2001 From: Ruben Bridgewater Date: Wed, 13 Apr 2016 03:46:51 +0200 Subject: [PATCH] Don't expose internal variables --- README.md | 15 ++------------- 1 file changed, 2 insertions(+), 13 deletions(-) diff --git a/README.md b/README.md index 8bbbd50..d2b82a0 100644 --- a/README.md +++ b/README.md @@ -613,27 +613,16 @@ All commands are sent as multi-bulk commands. `args` can either be an Array of a Boolean tracking the state of the connection to the Redis server. -## client.command_queue.length +## client.command_queue_length The number of commands that have been sent to the Redis server but not yet replied to. You can use this to enforce some kind of maximum queue depth for commands while connected. -Don't mess with `client.command_queue` though unless you really know what you are doing. - -## client.offline_queue.length +## client.offline_queue_length The number of commands that have been queued up for a future connection. You can use this to enforce some kind of maximum queue depth for pre-connection commands. -## client.retry_delay - -Current delay in milliseconds before a connection retry will be attempted. This starts at `200`. - -## client.retry_backoff - -Multiplier for future retry timeouts. This should be larger than 1 to add more time between retries. -Defaults to 1.7. The default initial connection retry is 200, so the second retry will be 340, followed by 578, etc. - ### Commands with Optional and Keyword arguments This applies to anything that uses an optional `[WITHSCORES]` or `[LIMIT offset count]` in the [redis.io/commands](http://redis.io/commands) documentation.