-
Notifications
You must be signed in to change notification settings - Fork 8
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
swift: add core #285
Merged
Merged
swift: add core #285
Changes from 1 commit
Commits
Show all changes
11 commits
Select commit
Hold shift + click to select a range
8ddd1a6
swift: add MQTT unsubscribe
fsuc 7db4eb8
swift: move message received closure to a property
fsuc f91f11d
swift: manage MQTT user property
fsuc 155153b
swift: add Core to use MQTT client with telemetry
fsuc 94c07d2
swift: add Core configuration
fsuc 97f4abf
swift: add Core integration tests
fsuc 7e7fac0
swift: add documentation on Core public items
fsuc fd889c3
swift: add a CoreMQTTMessage public initializer
fsuc 083f4c2
swift: disconnect after MQTT connection in tests
fsuc 3df8822
swift: add a default value without telemetry
fsuc b39b38c
swift: add localized description in MQTTClientError
fsuc File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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
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
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
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
If I understand correctly, this guard ensures that we can only unsubscribe (but there is the same guard on the subscribe) when the MQTT client is actually connected.
This has too implications, both not very pleasant:
What would be a better solution is to actually keep the list of subscriptions as a "private member" in the MQTT client object, and allow the user of the SDK to manipulate that list at will (by way of calling
subscribe()
andunsibscribe()
). Then when the MQTT client gets connected, it requests those subscriptions to the broker.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
For the first point the library does the same : it launches an exception if not connected so it would be the same result without the guard for all the operations.
I plan to manage the disconnection later because there are two main options:
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Option retained : 2 for a future PR.
Update subscriptions list and skip published message when reconnecting.