Improve MQTT documentation (#2967)

This commit is contained in:
Johan Ström 2019-11-21 12:38:07 +01:00 committed by Marcel Stör
parent 1759ebb360
commit e9199a5316
1 changed files with 2 additions and 2 deletions

View File

@ -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