proper implementation of custom persistence - "c-" messages remaining in the db after delivery
#1415
Replies: 1 comment
-
|
sorry it was my mis-understanding, no problems. |
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
-
We have implemented sqlite3 db user persistence.
We have observed that after messages are delivered/published the PERSISTENCE_COMMAND_KEY variety of the messages are left stacking up in the sqlite3 db; ie. "c-5",
Is this intended? Should the client application remove these messages from functionality in the callback MQTTAsync_deliveryComplete?
Many thanks!
Beta Was this translation helpful? Give feedback.
All reactions