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
Copy file name to clipboardExpand all lines: docs/modules/mqtt.md
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -157,8 +157,8 @@ end
157
157
158
158
In reality, the connected function should do something useful!
159
159
160
-
The two callbacks to `:connect()`alias with the "connect" and "offline"
161
-
callbacks available through `:on()`.
160
+
The first callback to `:connect()`aliases with the "connect" callback available through `:on()` (the last passed callback to either of those are used).
161
+
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.
162
162
163
163
Previously, we instructed an application to pass either the *integer* 0 or
164
164
*integer* 1 for `secure`. Now, this will trigger a deprecation warning; please
0 commit comments