[OASIS Issue Tracker] (MQTT-541) Cleansession should act like MQTT 5.0 not 3.1.1

[OASIS Issues Tracker <workgroup_mailer@lists.oasis-open.org>]

    [ https://issues.oasis-open.org/browse/MQTT-541?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=76859#comment-76859 ] 

Allan Stockdill-Mander edited comment on MQTT-541 at 5/6/20 11:54 AM:
----------------------------------------------------------------------

Discussed having these as multibyte values but decided that for ease of construction of packets and simplicity of implementation given that these are infrequently sent packets fixed size were a better choice.

Â

Rather this is the current preference, subject to revision based on future issues


was (Author: al.s-m):
Discussed having these as multibyte values but decided that for ease of construction of packets and simplicity of implementation given that these are infrequently sent packets fixed size were a better choice.

> Cleansession should act like MQTT 5.0 not 3.1.1
> -----------------------------------------------
>
>                 Key: MQTT-541
>                 URL: https://issues.oasis-open.org/browse/MQTT-541
>             Project: OASIS Message Queuing Telemetry Transport (MQTT) TC
>          Issue Type: Improvement
>          Components: MQTT-SN
>    Affects Versions: MQTT-SN-1.2
>            Reporter: Ian Craggs
>            Priority: Trivial
>
> The *clean session flag* operates in a similar manner to MQTT 3.1.1 in that the cleanup operates at both the start and end of the session. In MQTT 5.0, the clean session flag becomes the clean start flag, and a separate property _session expiry_ dictates when the session state is removed on the server. The MQTT 5.0 facilities are much more flexible and I would advocate changing MQTT-SN to match. One way to achieve this would be to add a session expiry 2 byte integer field (matching the _duration_ field) to the CONNECT packet.



--
This message was sent by Atlassian Jira
(v8.3.3#803004)