[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:comment-tabpanel&focusedCommentId=62249#comment-62249 ] 

Richard Coppen commented on MQTT-263:
-------------------------------------

Face to face discussion:

There are several things going on here:

1. Clearing state down to avoid discovery and negotiation of state on connect
2. Provide grace period before disconnect is processed (client might come back, so store my messages, but if not...)
3. Handling of WILL Message (with time axis)
4. ...also interaction with Jiras on message expiry MQTT-249
5. What's the maximum period a server will allow? do we need some form of discovery 

> 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)