mirror of https://github.com/taigrr/nats.docs synced 2025-01-18 04:03:23 -08:00

History

`ConnErrHandler` function prototype needs updating in example snippet

2020-02-12 18:02:19 +08:00

buffer.md

Update buffer.md

2020-02-06 12:11:50 -06:00

disable.md

GitBook: [master] 82 pages modified

2019-12-18 22:09:45 +00:00

events.md

Update events.md

2020-02-12 18:02:19 +08:00

max.md

Update max.md

2020-02-06 12:15:38 -06:00

random.md

Reword and add links

2020-02-05 18:20:39 -05:00

README.md

Update README.md

2020-02-06 12:07:45 -06:00

wait.md

Incorporating comments from PR

2020-02-09 15:40:13 -05:00

README.md

Automatic Reconnections

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, to notify about reconnect state and to inform about a new server.