From 5142b5f6ab77152b640fa431969d45ffe6854c28 Mon Sep 17 00:00:00 2001 From: Ginger Collison Date: Thu, 6 Feb 2020 12:07:12 -0600 Subject: [PATCH] Update README.md --- developing-with-nats/reconnect/README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/developing-with-nats/reconnect/README.md b/developing-with-nats/reconnect/README.md index 85e9387..48eed21 100644 --- a/developing-with-nats/reconnect/README.md +++ b/developing-with-nats/reconnect/README.md @@ -2,4 +2,4 @@ Most, if not all, of the client libraries will reconnect to the NATS system if they are disconnected for any reason. The reconnect logic can differ by library, so check your client library's documentation. -In general, the client will try to re-connect to one of the servers it knows about, either through the URLs provided in the `connect` call or the URLs provided by the NATS system during earlier connects. This feature allows NATS applications and the NATS system itself to self heal and reconfigure itself with no additional configuration or intervention. The library may have several options to help control reconnect behavior, notify about reconnect state and inform about new server. \ No newline at end of file +In general, the client will try to re-connect to one of the servers it knows about, either through the URLs provided in the `connect` call or the URLs provided by the NATS system during earlier connects. This feature allows NATS applications and the NATS system itself to self heal and reconfigure itself with no additional configuration or intervention. The library may have several options to help control reconnect behavior, notify about reconnect state and to inform about a new server.