Add option to control connection lifecycle based on active tab state

[chrismccord]

We can also supported a jittered reconnect when the tab is not active

[josevalim]

To give a bit more context, if the server disconnects (because of a deploy), a not active tab may still immediately reconnect and we may benefit from postponing it to reduce spikes on the server.

[SteffenDE]

To give a bit more context, if the server disconnects (because of a deploy), a not active tab may still immediately reconnect and we may benefit from postponing it to reduce spikes on the server.

If that's all we want to achieve, #6534 would fix this, as we'd only try to reconnect as soon as the tab becomes active again.

[josevalim]

Yup, agreed #6534 should solve this.

[hazolsky]

Hi all 👋

There is one issue with #6534 implementation — if connect() was never called on Socket instance (intentionally), visibility change to visible will trigger unintentional connect() call (bypassing app logic).

I'll try to find time to open a PR addressing this sometime later this week.

[SteffenDE]

Hey @hazolsky,

that was already fixed, we just need to do a new release. I’ll ping Chris to get one out soon :)

[hazolsky]

Glad to hear! Thanks @SteffenDE 🤝