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

No way to set properties on will message

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: 5, CSD01
    • Fix Version/s: 5, wd17
    • Component/s: core
    • Labels:
      None
    • Proposal:
      Hide

      The properties Payload Format Indicator, Publication Expiry, and Content Type on the CONNECT packet apply to the will message, as they are not otherwise used.

      A second property type UTF-8 String Pair on CONNECT called the Will User Property allows user properties of the will message to be set.

      Show
      The properties Payload Format Indicator, Publication Expiry, and Content Type on the CONNECT packet apply to the will message, as they are not otherwise used. A second property type UTF-8 String Pair on CONNECT called the Will User Property allows user properties of the will message to be set.

      Description

      There is no way to set properties on the will message. This may have been discussed but on implementation it seems like a significant omission and asymmetry. Content type and payload format, are two examples of properties which would be very useful.

      The behaviour of properties on retained messages appears to be unspecified. It could be interpreted that properties are not stored nor propagated, but that seems unlikely to be desirable. In the event of propagation, the behaviour of some properties such as the publication expiry interval, should be clarified. I suggest that the "time of receipt" for a retained message should be the time of receipt of the subscribe request which triggers it.

        Attachments

          Activity

            People

            • Assignee:
              ken.borgendale Ken Borgendale (Inactive)
              Reporter:
              icraggs Ian Craggs (Inactive)
            • Watchers:
              4 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: