-
Notifications
You must be signed in to change notification settings - Fork 6.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
MQTT client capability: QoS1, QoS2 #1970
Comments
by Flavio Santes: MQTT QoS 0, 1 and 2 is in testing. This code is on top of GH-2015. |
by Flavio Santes: So far, we are blocked by GH-2067. This issue breaks the build system for applications requiring source files in directories other than src. |
by Flavio Santes: GH-2067 was fixed by https://gerrit.zephyrproject.org/r/#/c/2923/ |
by Lei Liu: MQTT Publish QoS0, QoS1, QoS2 message. MQTT subscribe QoS0, QoS1, QoS2 topic 1470581266: Received SUBSCRIBE from zephyr Zephyr: v1.5.0-rc1 |
References GH-1779 |
Related to GH-1779 |
Related to GH-2099 |
Related to GH-2104 |
Reported by Anas Nashif:
As a user, I want to use Zephyr to send data using MQTT to a broker with quality of services 1 and 2.
MQTT uses a “publish/subscribe” model and requires a central MQTT broker to manage and route messages among an MQTT network’s nodes. Eclipse describes MQTT as “a many-to-many communication protocol for passing messages between multiple clients through a central broker.” It uses TCP for its transport layer, which is characterised as “reliable, ordered and error-checked.”
QoS1, At least once: The message is always delivered at least once. It might be delivered multiple times if there is a failure before an acknowledgment is received by the sender. The message must be stored locally at the sender, until the sender receives confirmation that the message has been published by the receiver. The message is stored in case the message must be sent again.
QoS2, Exactly once: The message is always delivered exactly once. The message must be stored locally at the sender, until the sender receives confirmation that the message has been published by the receiver. The message is stored in case the message must be sent again. QoS2 is the safest, but slowest mode of transfer. A more sophisticated handshaking and acknowledgement sequence is used than for QoS1 to ensure no duplication of messages occurs.
(Imported from Jira ZEP-416)
The text was updated successfully, but these errors were encountered: