Skip to content

Conversation

JonahLuckett
Copy link
Contributor

May be redundant due to the current inability to use MQTTv5 but this way we're ready for the node update if we wanted to be.

May be redundant due to the current inability to use MQTTv5 but this way we're ready for the node update if we wanted to be.
@JonahLuckett JonahLuckett requested a review from durera July 18, 2019 22:45
@durera
Copy link
Contributor

durera commented Dec 23, 2019

After various discussions today, have decided that we'll support MQTTv5 by making it a replacement for v3.1.1 rather than an alternative/configuration option ... supporting multiple versions will create additional overheads in terms of testing and code paths that we'll need to maintain as we start to take advantage of the v5 features, so after consideration we're going to tweak how we do this. Will discuss with you @JonahIBM once you're back from xmas hols .. should be a few simple tweaks we can make here to make it so that "it's just MQTT v5"

@herleraja herleraja force-pushed the master branch 3 times, most recently from 49e89cb to 34ff138 Compare August 8, 2025 10:32
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants