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

Ed Briggs commented on MQTT-304:
--------------------------------

1, The value of having an overall length field is that a system that wants to skip (ignore) the value can simply read the length, and advance the stream to the next item of interest. I believe there have been several discussions on the desirability of being able to do that, so I added the length.

2. The proposal is that these are processed by the application, so the interpretation of the items, including how to handle multiple instances of the same name should not be specified in the standard. The server should pass them as they are, in the order they were received. There is no impled order on any of the other metadata tags in any other JIRA (though must prohibit multiple instances of the same tag).  However, I think it would not serve a useful purpose for the server to re-order tags in a message it is forwarding.

3. The advantage of using UTF-8 is that the strings are 'counted strings' and we already have an existing type and code to process these.  To prevent an explosion in the number of types, value encoding, etc. I used UTF-8 strings. They're pretty flexible.  We could do a series of name=value with some separator. But if someone needs to use
the '=' or the separator character, we have to add an escape hack I'd like to avoid.



> 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)