[OASIS Issue Tracker] (MQTT-270) SN Feature: server initiated disconnects

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

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

Ian Craggs commented on MQTT-270:
---------------------------------

I was intentionally keeping the list of reason codes short, to mirror the approach of the CONNACK reason codes.   If the codes are fine grained, we might get requests to update the list frequently.  But I'm ok going with a longer list we can all agree on.  I had also envisaged that the reason codes would be used when sending from server to client, and not from client to server.

A question has also been raised as to which of the reason codes would trigger a will message.   As I think the intention of the will message is to allow the client application to take a closing action on an unexpected disconnection, I think they should all trigger a will message.  The only possible exception, I propose, could be on a fast shutdown if the sending of further messages was going to be disallowed anyway.

> SN Feature: server initiated disconnects
> ----------------------------------------
>
>                 Key: MQTT-270
>                 URL: https://issues.oasis-open.org/browse/MQTT-270
>             Project: OASIS Message Queuing Telemetry Transport (MQTT) TC
>          Issue Type: Improvement
>          Components: futures
>    Affects Versions: 3.1.1
>            Reporter: Ian Craggs
>            Assignee: Ian Craggs
>
> MQTT-SN allows the server to send a disconnect packet to a client. This is much nicer behaviour, for example in the case that a server is shutting down. A reason could also be transmitted with the disconnect packet, so that the client had some idea of when to attempt to reconnect. 



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