Connection state not changed on Windows about pusher-js HOT 2 CLOSED

Thanks a lot for reporting this. I'll look into it.

from pusher-js.

Hi Dumitru,

Thanks again for reporting this. I've looked into it. Using Google Chrome 18 and Windows 7, I was able to reproduce this behaviour intermittently. The short answer: in cases when the connection says it is connected but is not, we have a special ping/pong functionality that will resolve the situation. Are you using version 1.11.0 or higher? If so, you should be all set.

The JavaScript library periodically pings our servers. If it doesn't get a response, it will close the socket which will update the connection state to the correct value. The default wait for sending a ping is 120 seconds. If you want to have the situation corrected more rapidly, you can override the Pusher.activity_timeout by specifying a value for activity_timeout in the options object you pass when you instantiate the Pusher object.

The longer answer:

There is a browser API called window.navigator.onLine that we use to try and detect a dropped connection as quickly as possible. This works by the browser updating the .onLine status and emitting an online or offline event as soon as it detects that the program's connection to the internet has been dropped or opened. However, this API is not very reliable. In some browsers, it is not implemented at all. In the browsers in which it is implemented, .onLine being true can indicate only a connection to the local router, or even be just plain wrong.

from pusher-js.