Re:WebSockets vs. Server-Sent-Events vs. Long-Polling vs. We...
by Animats on Monday March 18, 2024 @11:39PM
(#39752716)
> with a user button
If the user ever has to push a "retry" button, the networking levels are very badly designed. Just because some crappy web sites work that way does not mean it's OK.
Re:WebSockets vs. Server-Sent-Events vs. Long-Polling vs. We...
by mjevans on Tuesday March 19, 2024 @03:22AM
(#39753610)
The user shouldn't _have_ to. However, a 'refresh state' (and validate state, more gracefully than a full kill and reload) button can be both helpful and psychologically reassuring.
It can also be very helpful for out of band issues, like ISP hiccups, random hardware failures, bitflips, etc.
Full Refresh; yes please, in the protocol, with a user button, with local client state cached client code and reloaded state on reconnect. Maybe even a configurable polling period; some services might offer shorter poll as a reason to pay for a higher tier account.