taigrr/nats.docs
1
0
Fork 0
mirror of https://github.com/taigrr/nats.docs synced 2025-01-18 04:03:23 -08:00
Code Issues Projects Releases Wiki Activity

Typo correction

Browse Source
This commit is contained in:
Dario Di Pasquale 2020-03-21 17:39:55 +01:00 committed by GitHub
parent 453fb0d4a7
commit a56550de9a
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 1 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
developing-with-nats/connecting/pingpong.md
View File

@ -4,7 +4,7 @@ The client and server use a simple PING/PONG protocol to check that either of th
![](../../.gitbook/assets/pingpong.svg) ![](../../.gitbook/assets/pingpong.svg)
Once a configurable maximum of outstanding pings without a single pong reply is hit, the connection is closed as stale. Together these two values define a timeout for the connection which specifies how quickly the client will be notified of a problem. This will also help when there is a remote network partition where the operating system does not detect a socket error. Upon connection close the client will attempt to reconnect. When it knows about other server, these will be tried next. Once a configurable maximum of outstanding pings without a single pong reply is hit, the connection is closed as stale. Together these two values define a timeout for the connection which specifies how quickly the client will be notified of a problem. This will also help when there is a remote network partition where the operating system does not detect a socket error. Upon connection close the client will attempt to reconnect. When it knows about other servers, these will be tried next.
In the presence of traffic, such as messages or client side pings, the server will not initiate the PING/PONG interaction. In the presence of traffic, such as messages or client side pings, the server will not initiate the PING/PONG interaction.