OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.


Help: OASIS Mailing Lists Help | MarkMail Help

mqtt message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]

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

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

Simon Johnson commented on MQTT-541:

I agree, the MQTT 5.0 behaviour is easier to understand and more powerful and would advocate this change.

The CONNECT packet presently looks like;


Could become;


> 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: Major
> 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

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]