[OASIS Issue Tracker] (MQTT-262) Clarify will messages if server disconnects

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

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

Ken Borgendale commented on MQTT-262:
-------------------------------------

I would argue that the V3.1.1 spec is quite clear on this:
The Will Message MUST be published when the Network Connection is subsequently closed unless the Will Message has been deleted by the Server on receipt of a DISCONNECT Packet

I interpret this to mean that if the server closes the connection for any reason other than receiving a DISCONNECT from the client it must send the will message.

So, the real point is how does a connection itself know that it has been closed because its clientID has been stolen.  In the case where this is actually a disconnect and reconnect from the same client, this is not an issue.  If this is a case of two clients trying to use the same clientID, this is a big problem.  The obvious solution is to send a DISCONNECT or similar packet from the server to the client with a return code and perhaps error data.  This would not guarantee that the client will do anything about it, but it at least gives the client the ability to do so.

> Clarify will messages if server disconnects
> -------------------------------------------
>
>                 Key: MQTT-262
>                 URL: https://issues.oasis-open.org/browse/MQTT-262
>             Project: OASIS Message Queuing Telemetry Transport (MQTT) TC
>          Issue Type: Improvement
>          Components: futures
>    Affects Versions: 3.1.1
>            Reporter: Raphael Cohen
>            Assignee: Raphael Cohen
>
> If a server disconnects a connection because a second client has connected with the same client id, should the first connections' will message be sent? I would argue it should, because this scenario is intended to reflect 'stuck' and 'hung' clients.



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