From d0283eac09dfdbb6b44450d8a6a025ed0d26518d Mon Sep 17 00:00:00 2001 From: mario solorzano Date: Wed, 18 Nov 2015 11:18:47 -0800 Subject: [PATCH] added stopRetrying clarification closes # 42 --- README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/README.md b/README.md index 9b23646..9b33ece 100644 --- a/README.md +++ b/README.md @@ -95,7 +95,7 @@ Set these variables in the `ipc.config` scope to overwrite or set default values | maxConnections| this is the max number of connections allowed to a socket. It is currently only being set on Unix Sockets. Other Socket types are using the system defaults. | | retry | this is the time in milliseconds a client will wait before trying to reconnect to a server if the connection is lost. This does not effect UDP sockets since they do not have a client server relationship like Unix Sockets and TCP Sockets. | | maxRetries | if set, it represents the maximum number of retries after each disconnect before giving up and completely killing a specific connection | -| stopRetrying| Defaults to false meaning clients will continue to retry to connect to servers indefinitely at the retry interval. If set to any number the client will stop retrying when that number is exceeded after each disconnect. If set to 0, the client will ***NOT*** try to reconnect. | +| stopRetrying| Defaults to false meaning clients will continue to retry to connect to servers indefinitely at the retry interval. If set to any number the client will stop retrying when that number is exceeded after each disconnect. If set to true in real time it will immediately irregardless of maxRetries. If set to 0, the client will ***NOT*** try to reconnect. | ----