Uploaded image for project: 'OASIS Message Queuing Telemetry Transport (MQTT) TC'
  1. OASIS Message Queuing Telemetry Transport (MQTT) TC
  2. MQTT-14

Tighten up language in Quality of Service levels and flows

    XMLWordPrintable

    Details

    • Type: Improvement
    • Status: Closed
    • Priority: Minor
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: None
    • Component/s: core
    • Labels:
      None
    • Proposal:
      Hide

      Remove sentence 1205 &1224 from "In the case of the Server it MUST make sure that it can honour the Qos requirements of the onward delivery" as this obvious and explained elsewhere in the spec.

      Replace with "On receipt, ownership of the Application Message is transferred to the Server. The Server MUST store the message in accordance to its Qos properties and ensure onward delivery to applicable subscribers."

      Originally reported under MQTT google group. https://mail.google.com/mail/?shva=1#inbox/13ec114a841305d9

      Show
      Remove sentence 1205 &1224 from "In the case of the Server it MUST make sure that it can honour the Qos requirements of the onward delivery" as this obvious and explained elsewhere in the spec. Replace with "On receipt, ownership of the Application Message is transferred to the Server. The Server MUST store the message in accordance to its Qos properties and ensure onward delivery to applicable subscribers." Originally reported under MQTT google group. https://mail.google.com/mail/?shva=1#inbox/13ec114a841305d9

      Description

      It was today reported in MQTT google group. https://mail.google.com/mail/?shva=1#inbox/13ec114a841305d9

      ----------
      The spec explains (http://public.dhe.ibm.com/software/dw/webservices/ws-mqtt/mqtt-v3r1.html#qos-flows) that when a message is published to the server with qos 1 the server should persist it, deliver it to all subscribers, delete the message and then puback.

      Does this require the server to wait for puback from all subscribers which subscribed with qos1 before sending puback to the original publisher? What about disconnected qos1 subscribers, are they exempted?

      My concern is that the pub/puback takes a whole lot longer in this case, without any extra reliability benefits. Couldn't the server send puback as soon as the message is persisted?
      ----------

      Language in specification needs to be tightened up

        Attachments

          Activity

            People

            • Assignee:
              ragupta2 Rahul Gupta
              Reporter:
              ragupta2 Rahul Gupta
            • Watchers:
              1 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: