Please add the supported QoS level of the library in the readme

[raffaeler]

I had to unfortunately discard this library because the old version did not support the highest QoS levels. Now I see there is an interesting update, but neither in the release notes or in the readme.md I can see the current supported level of QoS. Could you please add this info in the readme.md please? If now it is supported, it would be nice pointing to the docs/wiki/test case/sample with some clue on how to use it.

Thanks!

[chkr1011]

Do you mean Client or Server? The library supports all QoS levels. Do you have more details about what you are missing or do not understand?

[raffaeler]

Hi @chkr1011 I mean both. I extensively tried to use the library with QoS level 2 but it did not provide the "exactly once" behavior. Even QoS level 1 gave me problems. I opened an issue a very long time ago: https://github.com/dotnet/MQTTnet/issues/1303 and there are other issues of people trying to use QoS >=1 successfully. The workaround I wrote is not a real solution which shuld be inside the library itself.

One of the reason why I opened this thread is because you once wrote that sessions were needed to fully support QoS+storage in the library: https://github.com/dotnet/MQTTnet/issues/374#issuecomment-1023600244. It read the new library does have support for sessions and I am wondering if the library provides a transparent management of the QoS behavior.

If the library supports it and you believe that it works, please provide the related samples and docs as I am not alone here.

[chkr1011]

I will add samples soon. But in general all QoS levels are "supported". The ting is that you need to store QoS level 1 and 2 messages on your own before sending them. If the publish fails (exception) you must retry sending it on your own. The library will not do this automatically. The managed client has some rough implementation for this and requires that the storage interface is implemented properly (see options).