Hi,
Is it possible, when using setPollInterval(), to set the polling in the client-side UI to stop polling on a comms error, session expired, or other fatal connectivity error?
The reason is, that if the server goes down for a period of time, the client side keeps polling, and continually brings up Communications Error overlays in the browser (at least on FF). Eventually, this overwhelms the browser and causes it to hang. Since after the first error, the session cannot recover in any case, it would be good for the client to only show the first fatal error, then stop polling (and/or use a system redirect).
Any suggestions on how this might be achieved?
[Note: This behaviour is also relevant for the Refresher add-on, but as this is no longer maintained for 7.1+ in favour of the built-in setPollInterval(), it would make sense to incorporate it into the built-in polling functionality]
Hi,
Wow, no responses to this one?
This seems like quite a problem for any polling app.
The client browser could get disconnected for any number of reasons (not just the server going down).
Having it constantly overlaying messages seems superfluous, given that even if the server comes back up, it won’t fix the error (the session is finished, after all).
Anyone have any advice on how this might be more gracefully handled?
We saw the exact same problem and abandoned the idea of using polling, it definitly doesn’t handly error situations gracefully, so you’re not alone
We decided to use push, and are fleshing out the problems there, as it is the better technology.
Hi,
Thanks for the quick replies!
I’m no javascript expert, but is it possible to adjust the client-side script to break out of the loop (or exit completly) on a comms error?
Thanks,
Petrer
