Skip to content

Commit

Permalink
Add clarification about sending subsequent INFO by the server
Browse files Browse the repository at this point in the history 
Signed-off-by: Tomasz Pietrek <tomasz@nats.io>
  • Loading branch information
@Jarema
Jarema committed Oct 17, 2023
1 parent 01ca75d commit 331494d
Showing 1 changed file with 2 additions and 2 deletions.
4 changes: 2 additions & 2 deletions spec/connection.md
View file
Original file line number Diff line number Diff line change
Expand Up @@ -37,8 +37,8 @@ Ensuring a consistent way how Clients establish and maintain connection with the
3. Client sends [CONNECT][CONNECT] json.
4. Clients and Server start to exchange PING/PONG messages to detect if the connection is alive.

**Note** Server can send subsequent [INFO][INFO] on a ongoing connection.
Client needs to handle them approprietly and update server lists and server info.
**Note** If clients sets `protocol` field in [Connect][Connect] to equal or greater than 1, Server can send subsequent [INFO][INFO] on a ongoing connection.
Client needs to handle them appropriately and update server lists and server info.

#### Auth flow
TODO
Expand Down

0 comments on commit 331494d

Please sign in to comment.