You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In the websocket docs, it mentions MQTT syntax being accepted for subscriptions. However, it mentions nothing about how this MQTT support is implemented internally. This matters because MQTT defines 3 QoS levels that have different implications for how clients should be written
It's also possible that by MQTT syntax you mean you're just using the MQTT syntax and now actually following the protocol at all, but even in this case it would be nice if this was explicitly mentioned and possibly what QoS level the implementation maps to
The text was updated successfully, but these errors were encountered:
In the websocket docs, it mentions MQTT syntax being accepted for subscriptions. However, it mentions nothing about how this MQTT support is implemented internally. This matters because MQTT defines 3 QoS levels that have different implications for how clients should be written
It's also possible that by
MQTT syntax
you mean you're just using the MQTT syntax and now actually following the protocol at all, but even in this case it would be nice if this was explicitly mentioned and possibly what QoS level the implementation maps toThe text was updated successfully, but these errors were encountered: