[OASIS Issue Tracker] (MQTT-329) Remove the ID/Value Pair length field

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

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

Allan Stockdill-Mander commented on MQTT-329:
---------------------------------------------

https://github.com/eclipse/paho.mqtt.java/blob/mqttv5-new/org.eclipse.paho.mqttv5.common/src/main/java/org/eclipse/paho/mqttv5/common/packet/MqttPublish.java#L205

This is an example from the Java client of them having to do something similar, below is the current state of the go client

https://github.com/eclipse/paho.mqtt.golang/blob/v5/packets/connect.go



> Remove the ID/Value Pair length field
> -------------------------------------
>
>                 Key: MQTT-329
>                 URL: https://issues.oasis-open.org/browse/MQTT-329
>             Project: OASIS Message Queuing Telemetry Transport (MQTT) TC
>          Issue Type: Improvement
>            Reporter: Allan Stockdill-Mander
>            Priority: Minor
>
> The current spec requires an id/value pair length field indicating how many bytes constitute the id/value pairs in the controlpacket, prior to any payload that may be in the controlpacket as well. From an implementer's point of view this means allocating and building a buffer to hold this data so it can be counted and the value inserted logically prior to this buffer. This is particularly problematic as the value is a Variable Byte Integer so space in a larger control packet buffer cannot be preallocated then filled afterwards (same annoyance occurs with the remaining length field earlier in the control packet).



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