OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.

 


Help: OASIS Mailing Lists Help | MarkMail Help

mqtt message

[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:all-tabpanel ]

Ian Craggs updated MQTT-270:
----------------------------

    Proposal: 
The DISCONNECT packet is the final Control Packet sent by the Client to the Server, or by the Server to the Client.  When sent by the client, it indicates that the Client is disconnecting cleanly.  When sent by the server, the packet must include a one byte reason code, indicating the reason for the disconnection.

Reason code values
1 - Server shutting down
2 - Server temporarily unavailable - please try later
3 - Client actions caused disconnect

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