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=77331#comment-77331 ] 

Simon Johnson commented on MQTT-541:

Proposed new section;



Table 9: CONNECT Message
 The CONNECT message is sent by a client to setup a connection. Its format is shown in Table 9:
â Length and MsgType: see Section 5.2.
â Flags:
â DUP, QoS, Retain, TopicIdType: not used.
â Will: if set, indicates that client is requesting for Will topic and Will message prompting;
â *CleanStart*: same meaning as with MQTT, however extended for Will topic and Will message (see Section 6.3).
â ProtocolId: corresponds to the âProtocolNameâ and âProtocolVersionâ of the CONNECT message.
â Duration: same as with MQTT, contains the value of the Keep Alive timer.
â *SessionExpiryInterval: same with MQTT, contains the time the gateway will maintain the session*
â ClientId: same as with MQTT, contains the client id which is a 1-23 character long string which uniquely identifies the client to the server.

> 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
>            Assignee: Simon Johnson
>            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

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