[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=62239#comment-62239 ] 

Ed Briggs commented on MQTT-263:
--------------------------------

If the goal is to have a way to create a new persistent session in place of an old one (without going through the steps Peter lists above), I think it would be more direct to simply do this in the CONNECT->CONNACK exchange. There would be three types of CONNECT commands, 
new ephemeral (CleanSession=1),  reuse-existing or create (CleanSession = 0) or create new persistent (CleanSession= 2 - yes we need another bit from somewhere).

I think the timeout based approach is indirect, and can result in the client and server disagreeing on the type of session being used (i.e. if the DISCONNECT is lost).   Rather than adding a DISCONNECT_ACK, we can just do this in the CONNECT for which there is already a CONNACK. 

If on the other hand, the desire is to reset the session context during a single transport connection, we probably need a handshake so that both session partners agree on the session state.


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