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

Jonathan Levell commented on MQTT-304:
--------------------------------------

(In reply to previous comment):

1. Having an overall length means it takes 1 skips rather than two - I'm fairly ambivalent about that but have a mild preference for no overall length and lengths for each string (though a single string with a '=' separator and that separator being disallowed in names doesn't feel like a big restriction?)

2. I don't think there should be normative text about how duplicates are handled - but (especially in the case of publish) clients are going to represent these somehow and non-normative guidance about how to deal with duplicates in such a representative seems useful. In particular clients are likely to use a map/associative array/dictionary to represent these fields and we don't want security issues where validating applications check one version and applications are given a different one of the duplicates. If we could find a suitably non-constraining form of words, do people feel it would be harmless that if representing the key value pairs as a map, the last one in the message wins in the case of duplicates?



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