Assume publish response as ping response #128
Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This option should be needed due to high frequently traffic environment. When flood of messages are reached in this client, keep_alive! response may not reached until response timeout and causes MQTT::ProtocolException with "No Ping Response received for xxx seconds". Signed-off-by: Hiroshi Hatake <[email protected]>
cosmo0920
force-pushed
the
assume-publish-response-as-pingresp
branch
from
021b04a to
194a675
Compare
|
Cool! Exactly my case. Thx! |
phlegx
added a commit
to phlegx/ruby-mqtt
that referenced
this pull request
Sep 5, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Fixes #127
This option should be needed due to high frequently traffic environment.
When flood of messages are reached in this client,
keep_alive! response may not reached until response timeout and
causes MQTT::ProtocolException with "No Ping Response received for
xxx seconds".
Signed-off-by: Hiroshi Hatake [email protected]