Details
-
User Story
-
Resolution: Unresolved
-
P2: Important
-
None
-
5.10.1, 5.11.0
-
None
Description
Currently the module automatically does this step. If a publish with qos1/2 is received, we send back the puback/pubrel.
Especially for qos2 that might be dangerous as finalizing a qos2 message can imply that it has been processed and all requirements containing that message are met. One use case is payment via a qos2 message. You have to ensure that the transaction is done and then puback.
Hence, add an API which allows to enable manual release of a message.
This is even more important in MQTT 5.0 where you can specify the maximum of "open" messages before the broker starts sending a new one (batch messages).
Attachments
Gerrit Reviews
For Gerrit Dashboard: QTBUG-66599 | ||||||
---|---|---|---|---|---|---|
# | Subject | Branch | Project | Status | CR | V |
235639,7 | Add support for message status updates | dev | qt/qtmqtt | Status: MERGED | -2 | 0 |