-
Notifications
You must be signed in to change notification settings - Fork 2.3k
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
Clean start on first connection only #1479
Comments
Hi, @ralight , long time no see. What's meaning of |
MQTT v3 called the connect flag "clean start". This was changed to "clean session" in v3.1 and kept the same in v3.1.1. Now v5.0 has changed the name back to "clean start". So yes, for MQTT v3.1.1 clients this would affect the "clean session" flag behaviour, but calling it "clean start" seems like the best choice for the future. This is especially true because it only really makes sense for a v5.0 client, where clean start only affects the session when you connect, not when you disconnect. The rationale (which came up on an email that I've my answer pasted from), is to allow changing the behaviour from what happens currently (clean start is always set), to having it set on the first connection only. This allows the following:
Without this option, v5 clients can't make full use of the clean start feature. |
How about if you could configure the clean start behaviour something like this:
The text was updated successfully, but these errors were encountered: