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

Clarify language in 4.1.1 Non normative example

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Minor
    • Resolution: Fixed
    • Affects Version/s: 3.1.1
    • Fix Version/s: 5, wd13
    • Component/s: edits
    • Labels:
      None
    • Proposal:
      Hide

      I think the example is correct though it depends on where you place the emphasis as to how you interpret it. The point is that the message must get to the server in spite of failures, the following would this make it clearer.

      4.1.1 Non normative example
      For example, a user wishing to gather electricity meter readings may decide that they need to use QoS 1 messages because they need to protect the readings against loss over the network, however they may have determined that the power supply is sufficiently reliable that the data in the Client and Server can be stored in volatile memory without too much risk of its loss.

      Conversely a parking meter payment application provider might decide that the payment message should never be lost due to either the network or the client or systems failing. Consequently they require that all data are force written to non-volatile memory before being transmitted across the network.

      Show
      I think the example is correct though it depends on where you place the emphasis as to how you interpret it. The point is that the message must get to the server in spite of failures, the following would this make it clearer. 4.1.1 Non normative example For example, a user wishing to gather electricity meter readings may decide that they need to use QoS 1 messages because they need to protect the readings against loss over the network, however they may have determined that the power supply is sufficiently reliable that the data in the Client and Server can be stored in volatile memory without too much risk of its loss. Conversely a parking meter payment application provider might decide that the payment message should never be lost due to either the network or the client or systems failing. Consequently they require that all data are force written to non-volatile memory before being transmitted across the network.
    • Resolution:
      Hide

      Clarify the wording of this in version 5. This is now section 4.1.2.

      Show
      Clarify the wording of this in version 5. This is now section 4.1.2.

      Description

      Sathyan Doraiswamy pointed out:

      4.1.1 Non normative example
      For example, a user wishing to gather electricity meter readings may decide that they need to use QoS 1 messages because they need to protect the readings against loss over the network, however they may have determined that the power supply is sufficiently reliable that the data in the Client and Server can be stored in volatile memory without too much risk of its loss.
      Conversely a parking meter payment application provider might decide that there are no circumstances where a payment message can be lost so they require that all data are force written to non-volatile memory before it is transmitted across the network.

      in the highlighted text above "there are no circumstances ", the statement , i think, should read as "there are circumstances" .. ("no" should be taken out)
      since there are circumstances where message can be lost, so they require all data to be writted to non-volatile memory.. correct?

        Attachments

          Activity

            People

            • Assignee:
              ken.borgendale Ken Borgendale (Inactive)
              Reporter:
              Andrew_Banks Andrew Banks
            • Watchers:
              2 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: