OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.


Help: OASIS Mailing Lists Help | MarkMail Help

mqtt-comment message

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

Subject: Re: [mqtt-comment] UNSUBALL : Cancel all subscriptions.

Hi Nagesh,

Thank you for your feedback and suggestions for MQTT 3.1.1.
I have raised Jira issue MQTT 237 for the TC to evaluate. You can track it via this link > https://issues.oasis-open.org/browse/MQTT-237 <

Many thanks


From:        ನಾಗೇಶ್ ಸುಬ್ರಹ್ಮಣ್ಯ (Nagesh S) <nageshblore@gmail.com>
To:        mqtt-comment@lists.oasis-open.org
Date:        07/08/2014 12:27
Subject:        [mqtt-comment] UNSUBALL : Cancel all subscriptions.
Sent by:        <mqtt-comment@lists.oasis-open.org>

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 ?


Unless stated otherwise above:
IBM United Kingdom Limited - Registered in England and Wales with number 741598.
Registered office: PO Box 41, North Harbour, Portsmouth, Hampshire PO6 3AU

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