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

From
OASIS Issues Tracker <>
Date
2016-07-12T15:46:53+00:00
ID
Thread
[OASIS Issue Tracker] (MQTT-270) SN Feature: server initiated disconnects
[ https://issues.oasis-open.org/browse/MQTT-270?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=62905#comment-62905 ] 

Ed Briggs commented on MQTT-270:
--------------------------------

I've added DISCONNECT error codes to MQTT-236.  The error codes I put in are a subset of those proposed by Ken above, becomes some were already covered by PUBACK, PUBREC, or CONNACK return codes (e.g. message too big).
Please have a look to see if you agree with my choices on this.

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