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-290) Session Expiry Will message.

     [ https://issues.oasis-open.org/browse/MQTT-290?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Andrew Banks updated MQTT-290:

There will be an id Value pair on CONNECT that describes the time in seconds, which is the delay between abnormal network disconnection and the publication of the will message. This is called the Will  Delay.

A zero rc disconnect clears the will message as today, this is normal disconnection.

If the client suffers abnormal disconnection then the will message is published after the minimum  of Will Delay seconds and Session expiry seconds.

This means there is no notification of session expiry after the client disconnects normally.
The Will message is effectively a Session Expiry message if the Will Delay is set to be longer than the Session Expiry and then the client disconnects abnormally.

> 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

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