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] Commented: (MQTT-5) Should the unused DUP, QoS, and RETAIN flags be zero in the CONNECT message?


    [ http://tools.oasis-open.org/issues/browse/MQTT-5?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=33349#action_33349 ] 

David Locke commented on MQTT-5:
--------------------------------

I might go one step further and mark the 3 bits as reserved for future use.  

The implication:-
the input doc has the a header on every command with three bits for DUP, QOS and RETAIN.  On connect and other commands these may be meaningless.  If meaningless why not make the use of the bits unique to each command.  In the case of Connect this could be "reserved for future use". 

This would then provide flexibility for adding features in the future such as flowing additional properties on connect... 

> Should the unused DUP, QoS, and RETAIN flags be zero in the CONNECT message?
> ----------------------------------------------------------------------------
>
>                 Key: MQTT-5
>                 URL: http://tools.oasis-open.org/issues/browse/MQTT-5
>             Project: OASIS Message Queuing Telemetry Transport (MQTT) TC
>          Issue Type: Improvement
>            Reporter: Andrew Banks
>
> Should the unused DUP, QoS, and RETAIN flags be zero in the MQTT Connect message? The current mqtt.org specification leaves this open. By 
> specifying that they must be zero we make it possible to put them to some use in the future.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://tools.oasis-open.org/issues/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        


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