Reset PUBLISH/PUBREL command's deadline interval when connection closed #302
Conversation
This file contains 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
|
@matsukaz thank you so much |
ckrey
pushed a commit
that referenced
this pull request
May 10, 2017
Release date 2017-05-10 [FIX] Fix random crashes on core data persistence #314 [FIX] use_frameworks! [FIX] Swift Tests output [FIX] CONNACK return codes [NEW] access publish data back messageDelivered is called? closes #296 [FIX] XCode 8.3.1 warnings and documentation [NEW] MQTT v5 properties [FIX] Reset PUBLISH/PUBREL command's deadline interval when connection closed #302 [NEW] initial version 5
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
When connection got closed after publishing message but before receiving PUBREC, stored messsage's deadline interval are set as DUPTIMEOUT (such as 20 sec).
This causes other messages that have never published overtakes the message after reconnection.
I've fixed this problem by resetting the message's deadline interval if connection got closed.