You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is there a way for publisher to get the acknowledgments from subscriber(s)? Let say the publisher expect 2 acks from 2 subscribers
Is my understanding correct that the QoS 2 only guarantees the message reaching to broker, but not necessary the subscribers right?
Why is this needed?
This is for the publisher to ensure the subscribers has received the message, and that it is not part of application code to implement this acknowledgement.
The text was updated successfully, but these errors were encountered:
Is my understanding correct that the QoS 2 only guarantees the message reaching to broker, but not necessary the subscribers right?
Your understanding is correct.
Is there a way for publisher to get the acknowledgments from subscriber(s)? Let say the publisher expect 2 acks from 2 subscribers
As far as I know, there is currently no such functionality. So, right now, I think you will have to relay on application logic to get such acknowledgments.
Perhaps, this is an extension that could be worth implementing in the feature. Can you explain why you need this to be implemented as part of EMQX rather than with application logic?
In MQTT, there is no builtin semantics for consumer confirmation. The specification however provided a mechanism and guidelines how to implement it with PUB/SUB primitives, check out request/response: https://www.emqx.com/en/blog/mqtt5-request-response
What would you like to be added or enhanced?
Hi EMQX team,
Is there a way for publisher to get the acknowledgments from subscriber(s)? Let say the publisher expect 2 acks from 2 subscribers
Is my understanding correct that the QoS 2 only guarantees the message reaching to broker, but not necessary the subscribers right?
Why is this needed?
This is for the publisher to ensure the subscribers has received the message, and that it is not part of application code to implement this acknowledgement.
The text was updated successfully, but these errors were encountered: