[OASIS Issue Tracker] (MQTT-237) Public review comment raised by Nagesh S

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

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

Richard Coppen commented on MQTT-237:
-------------------------------------

Take to TC call 21st August.

> Public review comment raised by Nagesh S
> ----------------------------------------
>
>                 Key: MQTT-237
>                 URL: https://issues.oasis-open.org/browse/MQTT-237
>             Project: OASIS Message Queuing Telemetry Transport (MQTT) TC
>          Issue Type: Bug
>          Components: core
>    Affects Versions: 3.1.1
>            Reporter: Richard Coppen
>
> Suppose, the MQTT protocol has another command - UNSUBALL. When the broker receives this command, it interprets it as multiple UNSUBSCRIBE command for every topic the given client has subscribed to. And, so in response, the broker sends those many UNSUBACK responses. Or, perhaps, one UNSUBALL with reason codes as 0 (all un-subscribed), 1 (total failure), 2 (partially un-subscribed) and topic strings that were unsubscribed.
> When developing a MQTT client, one can maintain a local store of the topics subscribed and then issue UNSUBSCRIBE to all these in a loop. However, with this command the overhead of maintaining such a store would be removed. A UNSUBALL allows an easy way for 'factory reset'.
> Can such a command be added ?
> Nagesh 



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