[ https://issues.oasis-open.org/browse/MQTT-290?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=63614#comment-63614 ]
Jonathan Levell commented on MQTT-290:
--------------------------------------
Discuss in the Sept2016 TC face to face seems to be moving towards consensus around having a timer on a will message, and the will message is sent at the minimum(will timeout, session timeout). Consensus wasn't complete but largely agreed.
Allowing a special return code that keeps will message allows the will message to be used to mark session expiry.
> Session Expiry Will message.
> ----------------------------
>
> Key: MQTT-290
> URL: https://issues.oasis-open.org/browse/MQTT-290
> Project: OASIS Message Queuing Telemetry Transport (MQTT) TC
> Issue Type: Improvement
> Components: futures
> Affects Versions: 5
> Reporter: Andrew Banks
> Assignee: Andrew Banks
>
> The Will message is created on CONNECT and is published by the Server
> if the network connection is lost without a DISCONNECT packet being
> processed.
> Jira 249 introduces the idea of a Session expiry interval, such that a
> session can be deleted by the client and server some time after
> an Network disconnection.
> This Jira discusses whether another Will message should flow when
> the client's Session is deleted. Possible approaches include:
> 1) Allowing a second Session Expiry will message to flow in the CONNECT packet,
> in addition to the current Network Disconnection will message,
> and publishing this when the session either expires or is deleted by an administrator.
> 2)Signaling via a flag in the CONNECT packet that the Will message
> should be published when the session expires or is deleted,
> instead of when the network is disconnected.
--
This message was sent by Atlassian JIRA
(v6.2.2#6258)
