• Type: New Feature
    • Resolution: No Action
    • Priority: Critical
    • None
    • Affects Version/s: 5
    • Component/s: futures
    • None
    • Hide

      Provide a way of publishing a set of messages indicating that they are numbered fragments of a larger message, transmitting and acknowledging each of the fragments independently. This enables the interleaving of other messages in between the fragments and also retransmission of only the interrupted fragment following a network disconnection.

      Show
      Provide a way of publishing a set of messages indicating that they are numbered fragments of a larger message, transmitting and acknowledging each of the fragments independently. This enables the interleaving of other messages in between the fragments and also retransmission of only the interrupted fragment following a network disconnection.
    • Hide

      No objections to closing this.

      Show
      No objections to closing this.

      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.

            Assignee:
            Andrew Schofield (Inactive)
            Reporter:
            Andrew Schofield (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            5 Start watching this issue

              Created:
              Updated:
              Resolved: