[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: [OASIS Issue Tracker] (MQTT-598) The SUBSCRIBE flag QoS should allow the QoS-1 value
[ https://issues.oasis-open.org/browse/MQTT-598?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=82363#comment-82363 ] Davide Lenzarini commented on MQTT-598: --------------------------------------- [~andysc]ÂYou are right about the fact, from chapter 3.19 of WD24, that the gateway must keep the QoS1/2 only messages. _During the asleep state, packets that need to be sent to the client are buffered at the server/gateway. The gateway MUST buffer application messages of quality-of-service 1 & 2._ _Non-normative comment_ _The gateway may choose to buffer messages of all quality-of-service 0, whilst the client is sleeping and is within itâs session expiry interva__l._ What I am trying to achieveÂisÂproviding a device in ASLEEP state publishing a PUBLISH-1 message the possibility to receive buffered messages that don't require any confirmation (so QoS-1 or QoS0). I close this ticket and open a new one focused on that. [~andysc]Thanks for your comments! They really helped me to refine the requirements I had in mind.  > 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)
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]