[OASIS Issue Tracker] (MQTT-508) The default for session expiry should be 0, not never

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

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

Andrew Banks commented on MQTT-508:
-----------------------------------

TC Meeting on Sept 21 agreed: 

- That flowing 0xFFFFFFFF (UINT_MAX)
is a special value that means the session does not expire.
-The not flowing a session expirey interval is equivalent to flowing  session expiry 0, hence the session expires immediately when the network connection is closed.

> The default for session expiry should be 0, not never
> -----------------------------------------------------
>
>                 Key: MQTT-508
>                 URL: https://issues.oasis-open.org/browse/MQTT-508
>             Project: OASIS Message Queuing Telemetry Transport (MQTT) TC
>          Issue Type: Improvement
>          Components: core
>    Affects Versions: 5, CSD01
>            Reporter: Ian Craggs
>            Priority: Minor
>             Fix For: 5
>
>
> If no session expiry property is included in the connect packet, then the default is assumed to be no expiry.  This could lead to applications unintentionally leaving client state on the server and never cleaning up.  This was the reason that the clean start flag was changed to clean session for later versions of MQTT.
> I think that it should be an effort for the application to leave session state lying around, rather than it being the easiest option.  In that vein, the default if no session expiry is included should be 0, not infinite. 
> This does pose the question of whether there should be a special value to indicate no expiry, other than max int.  But that may not be crucial or necessary. 



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