Connection problems (state_change and long running connection) about pusher-js HOT 8 CLOSED

+1 For a fix.

In my own code, I have a timer that uses the WS to send a 'backbeat' event. When the WS is disconnected, I get the disconnect notice and then it reconnects automatically.

from pusher-js.

I think we have something on our backlog about changing the way we do heartbeats on connections, I'm not sure what the current status of that task is, however.

from pusher-js.

+1 For a fix.

from pusher-js.

+1 For a fix.

from pusher-js.

+1 for a fix.

from pusher-js.

We're just about to announce the release of v1.11 of our JavaScript library. This adds improved connection monitoring which we believe will resolve a number of connection problems. For those watching this issue the release is available here:

http://js.pusher.com/1.11/pusher.min.js

_Note: hosting is now available on _js.pusher.com* and new releases of our library will only be pushed there - not to js.pusherapp.com*

from pusher-js.

Version 1.11 has been released. We've had no further reports of connection problems so I'm closing this issue.

from pusher-js.

Thank you!!

Thanks,
Lance
512-751-7201

Sent from my iPhone

On Jan 23, 2012, at 4:02 AM, Phil [email protected] wrote:

Version 1.11 has been released. We've had no further reports of connection problems so I'm closing this issue.

---

Reply to this email directly or view it on GitHub:
#11 (comment)

from pusher-js.