[OASIS Issue Tracker] (MQTT-598) The SUBSCRIBE flag QoS should allow the QoS-1 value

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

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

Andy Stanford-Clark edited comment on MQTT-598 at 1/16/23 3:25 PM:
-------------------------------------------------------------------

Thanks for the explanation, but I do not see the use case:

With a persistent subscription (clean session false), a broker only has to hold pending messages of QoS 1 or 2. Anything lower than that (0 and -1, presumably) it can throw away if no subscribers to that topic are connected.

So I do not think there will ever be "pending" QoS -1 messages in the broker.
You mentioned "when the client publishes a QoS -1 message", so do you mean another client will receive that "trigger" and then start sending messages which this client should receive because of its QoS -1 subscription?

I just can't see why you would want/need to do this - if you want to receive messages, surely you should expect to be connected and awake?

Â

Perhaps I'm still missing your point?


was (Author: andysc):
Thanks for the explanation, but I do not see the use case:

With a persistent subscription (clean session false), a broker only has to hold pending messages of QoS 1 or 2. Anything lower than that (0 and -1, presumably) it can throw away if no subscribers to that topic are connected.

> The SUBSCRIBE flag QoS should allow the QoS-1 value
> ---------------------------------------------------
>
>                 Key: MQTT-598
>                 URL: https://issues.oasis-open.org/browse/MQTT-598
>             Project: OASIS Message Queuing Telemetry Transport (MQTT) TC
>          Issue Type: Improvement
>            Reporter: Davide Lenzarini
>            Priority: Major
>
> A client should be able to subscribe to a topic with QoS-1, this way it would be possible for it to receive Application Messages also when in status âasleepâ immediately after it sends a Publish QoS-1.Â



--
This message was sent by Atlassian Jira
(v8.3.3#803004)