Pusher connections stack up when using Turbolinks

[barmstrong]

Saw a similar issue here: chrismccord/render_sync#48

Seems to also happen using pusher with the popular Pusher gem https://github.com/rails/turbolinks/

I have the Pusher Javascript set up in a $(document).ready(... in the body of my page.

I'm thinking there might be a solution here around switching the load event or having the gem intelligently disconnect.

[mloughran]

Can you report this on https://github.com/pusher/pusher-js instead - this ruby gem has nothing to do with the browser connection.

However, I would have thought that if one was using turbolinks one would want to reuse the same pusher connections across multiple 'page loads' for efficiency?

[mloughran]

Closing