-
-
Notifications
You must be signed in to change notification settings - Fork 228
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
The QoS of retained messages should depend on subscribers (#288)
* Enhance retain test broker not store zero-byte retained messages * Send retained packets should incr broker.counter. * clientSub.qos=0 should not be evaluated as false * Retained messages delivery QoS should depend on subscribers [MQTT-3.3.1-5] 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 We store the retained message QoS in a persistence store. If the retain message is QoS 1 Sub (QoS 2) will get the msg in QoS 1 Sub (QoS 1) will get the msg in QoS 1 Sub (QoS 0) will get the msg in QoS 0 (downgraded) * Refactored & standardized * Added comment * Fixed lint * Fixed test that subscription happen after retained
- Loading branch information
Showing
3 changed files
with
91 additions
and
19 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters