[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=59231#comment-59231 ] Rick Bullotta commented on MQTT-252: ------------------------------------ We've done it multiple ways. Chunked transmission over XMPP or WebSockets, HTTP, FTP, you name it. Usually it's best to do those transfers OOB if possible. A similar scenario exists if you want to use the same connection (or communications channel) for streaming or tunneling (video, remote desktop, SSH, 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 (v6.2.2#6258)
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]