| [paho-dev] Outgoing message queue |
|
Hi all,
for one of our projects we're using paho-c on a linux based device and it is working as expected, except for a small aspect. When the connection is missing, paho pretends to store outgoing messages into a list and manages the list by it's own. The number of max messaged to be inserted seems to be ruled by MQTTClient_SSLOptions.reliable evaluation and if it's "true" the max number of messages is 1, else 10. That means if we have 15 messages to send and MQTTClient_SSLOptions.reliable == "false", when connection is missing only the oldest 10 messages are stored.
Our device is an IoT device and what we would achieve is to be able to decide what to do with unsent data. We'd like to apply policies
based on the type of data we're going to send because some type of data needs just last valid value and, in this case, it's a waste of traffic data to send old data.
So here's my question: How can we control the destiny of unsent data? Is there a way to manipulate the outboundMsgs list from public APIs?
Thank you for the attention and best regards, Denis Brachet Barbuse |