[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: [OASIS Issue Tracker] (MQTT-243) Wording in 3.3.1.3 might be clearer (review comment from Nicholas Humfrey)
[ https://issues.oasis-open.org/browse/MQTT-243?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=43660#comment-43660 ] Richard Coppen commented on MQTT-243: ------------------------------------- lines 755-762: If the RETAIN flag is set to 1, in a PUBLISH Packet sent by a Client to a Server, the Server MUST store the Application Message and its QoS, so that it can be delivered to future subscribers whose subscriptions match its topic name [MQTT-3.3.1-5]. When a new subscription is established, the last retained message, if any, on each matching topic name MUST be sent to the subscriber [MQTT-3.3.1-6]. If the Server receives a QoS 0 message with the RETAIN flag set to 1 it MUST discard any message previously retained for that topic. It SHOULD store the new QoS 0 message as the new retained message for that topic, but MAY choose to discard it at any time - if this happens there will be no retained message for that topic [MQTT-3.3.1-7]. See Section 4.1 for more information on storing state. > Wording in 3.3.1.3 might be clearer (review comment from Nicholas Humfrey) > -------------------------------------------------------------------------- > > Key: MQTT-243 > URL: https://issues.oasis-open.org/browse/MQTT-243 > Project: OASIS Message Queuing Telemetry Transport (MQTT) TC > Issue Type: Improvement > Components: core > Affects Versions: 3.1.1 > Reporter: Richard Coppen > > Public review comment received from Nicholas Humfrey (point 6) > 6) Also in section 3.3.1.3, I found the language used confusing - I > don't think it is clear that messages with any QoS should be retained, > not just QoS 0. -- This message was sent by Atlassian JIRA (v6.2.2#6258)
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]