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
Clients need to react to the library changing state to disconnecting as opposed to waiting for the state to transition into disconnected (this transition takes a long time and the interval is not configurable).
The text was updated successfully, but these errors were encountered:
@topliceanu hi, can I just try and clarify your use case here...I'm pretty certain that the only time that the connection state transitions from connected => disconnecting => disconnected is when you explicitly call disconnect on the client. In this case it should be trivial enough for you to handle this transition in your own code (start reacting after calling disconnect and wait for the delegate callback to inform you that it has disconnected).
In all other cases of disconnection or connection failure the library should transition immediately to disconnected. Are you not seeing this? What interval are you referring to and what specifically is taking a long time?
@lukeredpath sorry for the confusion, let me try to explain the issue again. I need a way to figure out when the library detects a lost connection, ie. switches from connected to disconnecting. I'm guessing libPusher can do it without me calling .disconnect(), for instance, when it does not receive a reply to a ping.
Clients need to react to the library changing state to
disconnecting
as opposed to waiting for the state to transition intodisconnected
(this transition takes a long time and the interval is not configurable).The text was updated successfully, but these errors were encountered: