OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.


Help: OASIS Mailing Lists Help | MarkMail Help

mqtt message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]

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

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

Raphael Cohen commented on MQTT-252:

The kind of devices using these sorts of chip sets aren't running Linux and don't have the capability for video streaming, remote desktops, etc. I'm sorry to be so oblique but I'm sharing information from an implementer - so I can't name names, etc.

> 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: 3.1.1
>            Reporter: Andrew Schofield
> 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

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]