Higher-level init function

[KyleAMathews]

There's more concerns accumulating for initing & maintaining a connection to Electric from the client e.g. picking a db name, and creating the client and now as of 0.9.4, connecting and re-connecting on the token expiring. This is what my initElectric function looks like — KyleAMathews/electric-query@8721875

It seems like these concerns could be pulled into electric itself as most everyone would do the same thing?

[thruflo]

Would be nice to have convenience functions for this (and for handling the auth reconnect).

[kevin-dp]

Hi @KyleAMathews,
As you raised before on Discord, JWTs are usually short-lived so using the JWT's expiration to dictate the end of the session is not a good idea. Based on your input, we decided to use the JWT only for authentication and we will need to introduce support for sessions. So you should not worry about the JWT expiring as we no longer close the connection when the JWT expires (the JWT's expiration is merely used as a deadline for authenticating). When we add support for sessions, programmers will need to handle expiration and renewal and we will document that accordingly.

Does this make sense?

Regards,
Kevin

[kevin-dp]

Yes, ofcourse if you re-connect the token you pass needs to still be valid so it may require fetching a new token.

[KyleAMathews]

ok, this is what I changed it to — look good? KyleAMathews/electric-query@02f9884

[KyleAMathews]

actually switched to https://github.com/GoogleChromeLabs/page-lifecycle from visibilitychange as that event doesn't capture when you alt-tab (or otherwise) enter an app, only when switching between tabs.

[KyleAMathews]

It's working well now with the page-lifecycle lib. I open my browser to a electric app and it now immediately reconnects.

[kevin-dp]

Looks good!