It would be quite important to be able to define the default QOS level to connect to in each connection instance saved against a server.
We have detected that against AMQ for example, the subscription is done in "queue" mode by default, and even if the mqttexplorer is closed, the AMQ seems to keep trying to send msg to that client.
this is a problem in environments with a bit high volume of msg.
Is there a forecast to be able to mark a subscription as durable true or false in future versions?
Thanks! It's a very good project anyway, and your effort is appreciated!
It would be quite important to be able to define the default QOS level to connect to in each connection instance saved against a server.
We have detected that against AMQ for example, the subscription is done in "queue" mode by default, and even if the mqttexplorer is closed, the AMQ seems to keep trying to send msg to that client. this is a problem in environments with a bit high volume of msg.
Is there a forecast to be able to mark a subscription as durable true or false in future versions? Thanks! It's a very good project anyway, and your effort is appreciated!