[OASIS Issue Tracker] (MQTT-252) Support for large message transmission

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

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

Brian Raymor commented on MQTT-252:
-----------------------------------

Note from the April F2F: Consider a set of recommendations e.g., non-normative or committee note to describe how an application can achieve this type of scenario. A couple of minor enhancements to protocol such as priority could really help. Needs TC time to explore properly

> Support for large message transmission
> --------------------------------------
>
>                 Key: MQTT-252
>                 URL: https://issues.oasis-open.org/browse/MQTT-252
>             Project: OASIS Message Queuing Telemetry Transport (MQTT) TC
>          Issue Type: New Feature
>          Components: futures
>    Affects Versions: 5
>            Reporter: Andrew Schofield
>            Assignee: Andrew Schofield
>            Priority: Critical
>
> MQTT has an architected limit of 256MB for the message payload. In practice, transmitting a message this large is troublesome. First, the transmission of large messages ties up the network connection for a considerable time, potentially blocking smaller messages. Second, the longer a message takes to transmit, the higher the chance that a network outage will interrupt the transmission, which would then have to be restarted from the beginning. MQTT would make a good transport for delivery of large payloads, in particular device firmware, but only if they can be transmitted in a more manageable way.



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