[OASIS Issue Tracker] (MQTT-263) Simplified State Management

[OASIS Issues Tracker <workgroup_mailer@lists.oasis-open.org>]

     [ https://issues.oasis-open.org/browse/MQTT-263?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Andrew Banks updated MQTT-263:
------------------------------

    Proposal: 
The DISCONNECT packet has an optional Session State Expiry Interval, if present this overrides the value set on CONNECT.

Clean Session is renamed to Clean Start, this causes any existing Session State to be deleted on CONNECT but not on DISCONNECT.

A new flag SendWillOnSessionStateExpiry, is sent as a CONNECT optional value. If absent or false the will message is sent on network disconnection where no DISCONNECT packet is processed as today. If true the Will message is sent on Session Expiry, regardless of how this occurs.
Or
A new flag WillDelay, is sent as a CONNECT optional value. If absent the will message is sent on network disconnection where no DISCONNECT packet is processed as today. If present the Will message is sent after the specified interval so long as no new CONNECT is processed first.

The Server retains knowledge of the Session for the duration of Session Expiry, even if the Session Contains no Messages or Subscriptions.


  was:The DISCONNECT packet has an optional duration field, of two bytes, which indicates that the session state, if there is any, can be discarded by the Server after that number of seconds has elapsed after the receipt of the DISCONNECT packet.   The session state must not be discarded if the Client reconnects within the duration interval, with the clean session flag set to false.  If the duration field is set to 0, the session state may be discarded immediately.


> Simplified State Management
> ---------------------------
>
>                 Key: MQTT-263
>                 URL: https://issues.oasis-open.org/browse/MQTT-263
>             Project: OASIS Message Queuing Telemetry Transport (MQTT) TC
>          Issue Type: Improvement
>          Components: futures
>            Reporter: Peter Niblett
>
> There could be some more things we do in CONNECT and DISCONNECT to make it easier for client applications to manage stateful Sessions. For example we could consider an option on DISCONNECT that requests an immediate destruction of server state (e.g. pending messages and subscriptions)



--
This message was sent by Atlassian JIRA
(v6.2.2#6258)