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:comment-tabpanel&focusedCommentId=62457#comment-62457 ] 

Ken Borgendale commented on MQTT-270:

The point of these reason codes is to help problem determination when something goes wrong.  This is a very serious problem with MQTT.  With all of our other protocols we have methods to return what went wrong when something fails.  In HTTP for instance we have not only a status code but an arbitrary content field to return what the problem is.

In the various client and server environments in which MQTT is used, we have various levels of logging for problem determination on client and server, and this various over the life of the application.  The server almost always has logs, and small clients frequently do not,  However, it is often harder for application developers to get at the server logs, especially in shared infrastructure environments.  By passing error information in both directions we can make this available to app developers, and for clients in production which do not have any logging capability.  On the server side I have some number of log entries which say the connection was broken by the client.  I would really like to be able to be able to log the reason in the case the client intentionally closed the connection.

In the client to server direction, I assume that only the default (good) reason code disables will processing.    

> 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

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]