[OASIS Issue Tracker] (MQTT-249) Add expiry capabilities to MQTT.

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

    [ https://issues.oasis-open.org/browse/MQTT-249?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=62966#comment-62966 ] 

Jonathan Levell commented on MQTT-249:
--------------------------------------

From the point of view of implementing the server, this proposal concerns me as it allows a client to connect saying they want their state to be thrown away when they disconnect but on disconnect change their mind. 

This requires implementers be able either forego optimisations about keeping state for some clients non-persistent or to alter the persistence of the server-side state on disconnect. It would simplify the task of implementing it if either:

a) the  "Session State Expiry interval" on disconnect had to be lower than the one supplied on connect
OR
b) If it set to 0 on connect it MUST non be set to non-0 on disconnect

> Add expiry capabilities to MQTT.
> --------------------------------
>
>                 Key: MQTT-249
>                 URL: https://issues.oasis-open.org/browse/MQTT-249
>             Project: OASIS Message Queuing Telemetry Transport (MQTT) TC
>          Issue Type: Improvement
>          Components: futures
>    Affects Versions: 5
>            Reporter: Andrew Banks
>            Assignee: Andrew Banks
>
> MQTT has the ability to purge all of the session state on demand by using the clean session flag. This proposal is for a time based and more granular capability to clear up state.  
> Add capabilities to MQTT to allow for expiry of.
> 1) Messages.
> 2) Subscriptions.
> 3) All session state, for example if the client is disconnected for a time period then treat it as if it had connected with clean session true.  This is sometimes referred to as offline keep alive.



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