[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: [OASIS Issue Tracker] Updated: (MQTT-201) Remove unclear statement on Qos1 sender to Qos0 subscriber
[ http://tools.oasis-open.org/issues/browse/MQTT-201?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Rahul Gupta updated MQTT-201:
-----------------------------
Proposal:
Original Sentence
If the subscribing Client has been granted maximum QoS 0, then an Application Message originally published as QoS 2 might get lost on the hop to the Client, but the Server should never send a duplicate of that Message. A QoS 1 Message published to the same topic might either get lost or duplicated on its transmission to that Client.
Changed Sentence
If the subscribing Client has been granted a maximum QoS 0, then an Application Message originally published as QoS 2 or QoS1 might get lost on the hop to the Client, but the Server should never send a duplicate of that Message.
==================================
Original Sentence
MQTT delivers Application Messages according to the Quality of Service (QoS) levels defined here. The delivery protocol is symmetric, in the diagrams below the Client and Server can each take the role of either Sender or Receiver. In the case of the Client, "Deliver Application Message" means give the message to the application. In the case of the Server it means send a copy of the Message to each Client with a matching subscription.
Changed Sentence
MQTT delivers Application Messages according to the Quality of Service (QoS) levels defined here. The delivery protocol is symmetric, in the diagrams below the Client and Server can each take the role of either Sender or Receiver. In the case of the Client, "Deliver Application Message" means give the message to the application. In the case of the Server it means send a copy of the Message to each Client with a matching subscription. QoS levels are only applicable for a single hop between a Sender or Receiver and not for an end to end transmission.
was:
Original Sentence
If the subscribing Client has been granted maximum QoS 0, then an Application Message originally published as QoS 2 might get lost on the hop to the Client, but the Server should never send a duplicate of that Message. A QoS 1 Message published to the same topic might either get lost or duplicated on its transmission to that Client.
Changed Sentence
If the subscribing Client has been granted a maximum QoS 0, then an Application Message originally published as QoS 2 or QoS1 might get lost on the hop to the Client, but the Server should never send a duplicate of that Message.
==================================
Original Sentence
MQTT delivers Application Messages according to the Quality of Service (QoS) levels defined here. The delivery protocol is symmetric, in the diagrams below the Client and Server can each take the role of either Sender or Receiver. In the case of the Client, "Deliver Application Message" means give the message to the application. In the case of the Server it means send a copy of the Message to each Client with a matching subscription.
Changed Sentence
MQTT delivers Application Messages according to the Quality of Service (QoS) levels defined here. The delivery protocol is symmetric, in the diagrams below the Client and Server can each take the role of either Sender or Receiver. In the case of the Client, "Deliver Application Message" means give the message to the application. In the case of the Server it means send a copy of the Message to each Client with a matching subscription. QoS levels are only applicable for a single hop between a Sender or Receiver and not for an end to end integration.
> Remove unclear statement on Qos1 sender to Qos0 subscriber
> ----------------------------------------------------------
>
> Key: MQTT-201
> URL: http://tools.oasis-open.org/issues/browse/MQTT-201
> Project: OASIS Message Queuing Telemetry Transport (MQTT) TC
> Issue Type: Improvement
> Components: edits
> Reporter: Allan Stockdill-Mander
> Assignee: Rahul Gupta
>
> Line 1155-1156 in wd19 says "A QoS 1 Message published to the same topic might either get lost or duplicated on its transmission to that Client." There is no concept of duplicate messages with QoS 0 and the the QoS guarantees are only over a single message hop, not end to end so this line should be removed.
> Line 1349 in wd19 should also state explicitly that QoS levels and mechanisms are only applicable to a single hop (such as sending client to server) rather than end to end (sending client to receiving client)
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://tools.oasis-open.org/issues/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]