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

Session Expiry Will message.

    XMLWordPrintable

    Details

    • Type: Improvement
    • Status: Closed
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: 5
    • Fix Version/s: None
    • Component/s: futures
    • Labels:
      None
    • Proposal:
      Hide

      There will be an id Value pair on CONNECT that describes the time in seconds, which is the delay between abnormal network disconnection and the publication of the will message. This is called the Will Delay.
      If not set zero Will delay is assumed.

      A zero rc disconnect clears the will message as today, this is normal disconnection.

      If the client suffers abnormal disconnection then the will message is published after at least the Will Delay seconds or when the Session expires, whichever happens first.

      This means there is no notification of session expiry after the client disconnects normally.
      The Will message is effectively a Session Expiry message if the Will Delay is set to be longer than the Session Expiry and then the client disconnects abnormally.

      Add a new disconnect return code which the client to flow which causes an abnormal disconnect, with no actual error behind it. This has the effect of ending the connection but keeping the will message.

      Show
      There will be an id Value pair on CONNECT that describes the time in seconds, which is the delay between abnormal network disconnection and the publication of the will message. This is called the Will Delay. If not set zero Will delay is assumed. A zero rc disconnect clears the will message as today, this is normal disconnection. If the client suffers abnormal disconnection then the will message is published after at least the Will Delay seconds or when the Session expires, whichever happens first. This means there is no notification of session expiry after the client disconnects normally. The Will message is effectively a Session Expiry message if the Will Delay is set to be longer than the Session Expiry and then the client disconnects abnormally. Add a new disconnect return code which the client to flow which causes an abnormal disconnect, with no actual error behind it. This has the effect of ending the connection but keeping the will message.
    • Resolution:
      Hide

      Included in WD07.

      Show
      Included in WD07.

      Description

      The Will message is created on CONNECT and is published by the Server
      if the network connection is lost without a DISCONNECT packet being
      processed.

      Jira 249 introduces the idea of a Session expiry interval, such that a
      session can be deleted by the client and server some time after
      an Network disconnection.
      This Jira discusses whether another Will message should flow when
      the client's Session is deleted. Possible approaches include:

      1) Allowing a second Session Expiry will message to flow in the CONNECT packet,
      in addition to the current Network Disconnection will message,
      and publishing this when the session either expires or is deleted by an administrator.

      2)Signaling via a flag in the CONNECT packet that the Will message
      should be published when the session expires or is deleted,
      instead of when the network is disconnected.

        Attachments

          Activity

            People

            • Assignee:
              andrew_banks Andrew Banks (Inactive)
              Reporter:
              andrew_banks Andrew Banks (Inactive)
            • Watchers:
              4 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: