Changed returntype of the Connect() function from byte to the complete Connack Message - Only way to determine the existence of the persistent session #137
+11
−11
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
Daniel900
changed the title
# for free
to join this conversation on GitHub.
Already have an account?
# 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.
The Code of the Client and MqttMsgConnack class already got changed to support the sessionPresent flag of mqtt v3.1.1.
But there is no way to get this flag, because the connect function just returns the return code and not the complete connack message.
This flag is very useful when working with persistent sessions to determine if a session already exists or every topic should be subscribed. (double subscription also works but if you have any retained messages (as I do) they'll get pulled twice)