Clustered LiveView app web socket

[MarthinL]

@LostKobrakai

You’re correct that there could be means to retain data, but it comes with all the complexities of caching, where store it, how long store it, …. It’s also slightly problematic to talk about first and second render, because it’s not two connections, it’s n connection. A single static render might connect over websocket multiple times in case of a connection drop. So do you retain the state of the static render up until a potential connection dropout, which could be any time later not just close in time.

Unless I’m gravely mistaken, I don’t see what I’ve proposed to suffer from the uncertainties and complications you’ve mentioned.

@LostKobrakai

If you think you have something to contribute that’s probably the best place to do so.

It remains to be seen if it’s worth anything but I went ahead and described my Proposed Session Handovers for LiveView on the issue