Commit e9199a53 authored by Johan Ström's avatar Johan Ström Committed by Marcel Stör
Browse files

Improve MQTT documentation (#2967)

parent 1759ebb3
...@@ -157,8 +157,8 @@ end ...@@ -157,8 +157,8 @@ end
In reality, the connected function should do something useful! In reality, the connected function should do something useful!
The two callbacks to `:connect()` alias with the "connect" and "offline" The first callback to `:connect()` aliases with the "connect" callback available through `:on()` (the last passed callback to either of those are used).
callbacks available through `:on()`. The second (failure) callback is however not the same as the "offline" `:on()` callback. The "offline" callback is only called after an already established connection becomes closed. If the `connect()` call fails to establish a connection, the callback passed to `:connect()` is called and nothing else.
Previously, we instructed an application to pass either the *integer* 0 or Previously, we instructed an application to pass either the *integer* 0 or
*integer* 1 for `secure`. Now, this will trigger a deprecation warning; please *integer* 1 for `secure`. Now, this will trigger a deprecation warning; please
......
Markdown is supported
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment