Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
To enable heartbeats, the client must create a new TuningSettings object
with a >= 1sec Duration value for the
heartbeatPeriod
field. TheTuningSettings must then be passed to the client's constructor via the
ConnectionSettings object.
During the initial connection handshake, the client will calculate the
effective heartbeat period (in seconds) by taking the minimum of the
heartbeat period values suggested by the client and the server.
Once a heartbeat interval has been negotiated between the client and the
server, the client will start sending heartbeat messages to the server
(approximately) twice within each heartbeat period. In addition, the
client also monitors incoming messages from the server. If no message
(heartbeat or not) has been received by the server within the heartbeat
period, the client will raise a
HeartbeatFailedException
.The following example illustrates how heartbeats can be enabled when creating a new client:
Fixes #71
Fixes #21