MQTT ExactlyOnce and AtLeastOnce
See original GitHub issueHello,
The MQTT protocol has 3 publish type. The last two (whose name are in the object), can inform the client that the message has been received with 100% of reliability.
Would be nice to have this information published, i.e. when using ::
public static Task PublishAsync(this IMqttClient client, params MqttApplicationMessage[] applicationMessages);
You should return some object result with SENT or not SENT information
JJ
Issue Analytics
- State:
- Created 6 years ago
- Comments:13 (6 by maintainers)
Top Results From Across the Web
What is MQTT Quality of Service (QoS) 0,1, & 2?
MQTT provides three levels of QoS: At most once (QoS 0); At least once (QoS 1); Exactly once (QoS 2). How to Examine...
Read more >Is Exactly-Once Delivery Possible with MQTT?
MQTT's optional QoS levels are to guarantee delivery no more than once (in which case you may miss a message), at least once...
Read more >MQTT ExactlyOnce and AtLeastOnce · Issue #61
A client that sends a QOS 3 message wants to be sure the server received it. It can be done using the MQTTNET...
Read more >Working with exactly once delivery | MQTT Essentials
Working with exactly once delivery. First, we will use wildcards to subscribe to a topic filter with QoS level 2 and then we...
Read more >MQTT QoS Guide - Quality of Service 0, 1, 2 Explained
This article covers the basics of MQTT QoS, what the differences are and ... QoS 0: at most once; QoS 1: at least...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found

@JTrotta OK please implement it as an extension. So a new Client wich uses the original client. Then users can decide to use the existing one or the new one with predefined rules. The actual MqttClient should as simple as possible.
Hi i have solve a problem but my client queued many nessage now i debug the application and after connect client to mqtt receive 1 message and stop, when I redebug a code receive another message, is possible clean the queued message I uso Mosquitto server