You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
At the moment if the response to a health-check does not come under the time specified by the user, the connection will timeout. This is not flexible enough to deal with e.g. heavy load where the specified interval cannot be honored because e.g. it is processing too many pushes.
We can offer two options to users
Inflexible checks: The connection times out if the specified interval is not honored. (Current implementation)
Flexibel checks: Any incoming data, like server pushes are seen as a proof of health (and not only the response to a health-check).
Option 2. covers my own needs, we might not need option 1.
The text was updated successfully, but these errors were encountered:
At the moment if the response to a health-check does not come under the time specified by the user, the connection will timeout. This is not flexible enough to deal with e.g. heavy load where the specified interval cannot be honored because e.g. it is processing too many pushes.
We can offer two options to users
Option 2. covers my own needs, we might not need option 1.
The text was updated successfully, but these errors were encountered: