[OASIS Issue Tracker] (MQTT-304) Metadata: Add User defined CONNECT data

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

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

Ken Borgendale commented on MQTT-304:
-------------------------------------

I do not see any particular value in having an overall length in addition to the name and value lengths.  This just makes it harder for someone writing this out.  My preference would be to have a single string value with a = character as the separator between name and value, but I guess any of these would work.

One concern I have is the meaning of having multiple of the same name.  It there an implied order?  Does the Server need to not only preserve the id/value pair but the order relative to other id/value pairs?  A common usage of this it to present a set of these properties as a Map and thus implement unique key names where setting the value replaces an existing one.

Jon suggested a use for these properties as bread crumbs, but even in that usage it seems better to use separate names which create an explicit order than to just have multiple properties of the same name.

Would it make sense that the value be binary data and not a UTF-8 string.  The only real difference is whether we do UTF-8 and null checking on the bytes.  Making the types of the name and value would be a reason to have two separate fields..

> Metadata: Add User defined CONNECT data
> ---------------------------------------
>
>                 Key: MQTT-304
>                 URL: https://issues.oasis-open.org/browse/MQTT-304
>             Project: OASIS Message Queuing Telemetry Transport (MQTT) TC
>          Issue Type: New Feature
>          Components: core
>    Affects Versions: 5
>            Reporter: Ed Briggs
>            Assignee: Ed Briggs
>              Labels: Proposed
>
> This was discussed in MQTT-276 with notes from the F2F meetings and has been tracked in MQTT-256.
> I'm opening a separate, specific issue per Ken's comments https://issues.oasis-open.org/browse/MQTT-256?focusedCommentId=62192page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-62192:
> "All of these would be defined in separate JIRAs, but what we should do in this JIRA is to define the mechanism used to pass these values." 



--
This message was sent by Atlassian JIRA
(v6.2.2#6258)