[OASIS Issue Tracker] Created: (MQTT-74) What should happen to messages pending delivery once the client sends unsubscribe?

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

What should happen to messages pending delivery once the client sends unsubscribe?
----------------------------------------------------------------------------------

                 Key: MQTT-74
                 URL: http://tools.oasis-open.org/issues/browse/MQTT-74
             Project: OASIS Message Queuing Telemetry Transport (MQTT) TC
          Issue Type: Improvement
          Components: core
    Affects Versions: 3.1.1
            Reporter: Richard Coppen
             Fix For: 3.1.1


A client might be too busy to process any more work, so sends UNSUBSCRIBE to turn the flow off. 
Alternatively, the client may be unaware that a backlog of messages exists and sends UNSUBSCRIBE. 

There are at lesat three possible options:

1. The server delays sending the UNSUBACK until the backlog is cleared
2. Send the UNSUBACK and then send the messages
3. Send the UNSUBACK and then purge the messages 

The client's last defense should it not want the messages is to disconnect and reconnect with cleanSession set to (1)



-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://tools.oasis-open.org/issues/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira