[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: [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=62579#comment-62579 ] Ian Craggs commented on MQTT-270: --------------------------------- 1) I think it's a good idea to have one set of return codes across the whole of MQTT packet types. In that case, a longer, more comprehensive list makes sense. 2) I'm not particularly in favour of allowing the client to send a reason code with its disconnect, especially if it complicates will processing. Rather than having an implicit link between reason codes and triggering the will message, I think it would be better to have an explicit flag to trigger the will message. > 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)
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]