Details

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

      In WD16 change section 3.1.2.5 to start ....

      If the Will Flag is set to 1.

      >>add to section 3.1.2.5<<
      The will message MUST be removed from the stored Session state in the Server once it has been published or the Server has received a DISCONNECT packet from the Client.
      If the Will Flag is set to 0, no will message is published.

      Show
      In WD16 change section 3.1.2.5 to start .... If the Will Flag is set to 1. >>add to section 3.1.2.5<< The will message MUST be removed from the stored Session state in the Server once it has been published or the Server has received a DISCONNECT packet from the Client. If the Will Flag is set to 0, no will message is published.

      Description

      In 3.1.2.3.2. there's a normative statement "
      The Will Flag indicates that a Will Message MUST be published by the server when the server detects that the client is disconnected for any reason other than the client flowing a DISCONNECT Packet [MQTT-3.1.2-7]"

      1. Editorial comment - This should say "If the Will Flag is set to 1, a Will Message MUST be published by the server when the server detects that the client is disconnected for any reason other than the client flowing a DISCONNECT Packet [MQTT-3.1.2-7]"

      2. Core comment. For the avoidance of doubt, we should say what happens if the Will Flag is 0

      I assume that the default is that no will message gets published, but if a server wants to use a $SYS topic to log unexpected disconnects, then it is free to do that, We should consider making it clear that a server does not "remember" the last Will Mesage / Topic that the client used.

        Attachments

          Activity

            People

            • Assignee:
              Unassigned
              Reporter:
              PeterNiblett Peter Niblett
            • Watchers:
              0 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: