Do something about potential queue flooding.

[dougkoellmer]

One can potentially flood the queue, putting tasks onto it faster than the queue can process them. Perhaps have enumerations for read/write/connect-fail callbacks indicating such a scenario, like if the queue has more than 100 tasks backed up. Actually maybe just for the read/write callback.

[c10h22]

Or maybe give some controls to developers to let them "clean" or to "empty" the queue when they need to so?

Or maybe give them the possibility to assign a kind of priority to some tasks like "High", "Medium", "Low" so some urgents tasks (like characteristic write) may be pushed to the top of the list to be executed?