From 55d883db6f10b6936724121d3b490bf06c45e98e Mon Sep 17 00:00:00 2001 From: Alberto Ricart Date: Mon, 20 Jul 2020 10:36:58 -0500 Subject: [PATCH] Updated `INFO` protocol to include `ldm` Added information about forthcoming `ldm` client notifications. --- nats-protocol/nats-protocol/README.md | 1 + 1 file changed, 1 insertion(+) diff --git a/nats-protocol/nats-protocol/README.md b/nats-protocol/nats-protocol/README.md index 170bca0..ad520cd 100644 --- a/nats-protocol/nats-protocol/README.md +++ b/nats-protocol/nats-protocol/README.md @@ -81,6 +81,7 @@ The valid options are as follows: * `tls_required`: If this is set, then the client must perform the TLS/1.2 handshake. Note, this used to be `ssl_required` and has been updated along with the protocol from SSL to TLS. * `tls_verify`: If this is set, the client must provide a valid certificate during the TLS handshake. * `connect_urls` : An optional list of server urls that a client can connect to. +* `ldm`: If the server supports _Lame Duck Mode_ notifications, and the current server has transitioned to lame duck, `ldm` will be set to `true`. #### connect\_urls