Replies: 1 comment
-
We currently fold in We fold trough all topic matches generated by an incoming topic (routing key), and then ask for the subscriber of a topic. This is a natural approach when we allow overlapping deliveries. To prevent those, we need to implement a alternative, grouping topics per subscriber before we deliver any message. Then we'd choose the subscription with the highest QoS to deliver the message once. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
From the 3.1.1 spec:
The VerneMQ approach is to deliver a message for every subscription, leaving the managing and consequences of overlapping subscriptions to the MQTT client.
We should look into the effort to make this behaviour configurable, both for MQTT 3.1.1 and MQTT 5 (where the spec has similar details, including the handling of provenience via Subscription identifiers).
Beta Was this translation helpful? Give feedback.
All reactions