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

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

Andrew Banks commented on MQTT-249:
-----------------------------------

See also MQTT-307 Clarify Handling of DISCONNECT Expiry interval error in WD04

> 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
>             Fix For: 5
>
>
> 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)