Disconnected from websocket - Printable Version +- Blitzortung.org Forum (https://forum.blitzortung.org) +-- Forum: Public Forums (https://forum.blitzortung.org/forumdisplay.php?fid=29) +--- Forum: Website, Maps and Applications (https://forum.blitzortung.org/forumdisplay.php?fid=24) +--- Thread: Disconnected from websocket (/showthread.php?tid=1636) |
Disconnected from websocket - DelandeC - 2016-03-05 Hi folks, Am I the only one who think this is too sad to be disconnected from the blitzortung websocket when I'm not on the window of blitzortung. It is impossible to have a dual screen with the map on one display and an other thing on the main display. Regards RE: Disconnected from websocket - kevinmcc - 2016-03-06 (2016-03-05, 17:38)DelandeC Wrote: Hi folks, You can fix this with Greasemonkey. I am sure they put the code the to reduce bandwidth taken up by hidden tabs and minimized windows. I am not sure how the devs will feel about people doing this, but the script is below. Code: // ==UserScript== RE: Disconnected from websocket - Egon - 2016-03-06 Hi, yes, the main problem is the huge data traffic. Up to June, this is not a big problem but if we have thunderstorms, then several thousands people start looking where it is, change the window, and do anything else. But the browser still continiously loads data. It is not only the huge data traffic but also the large number of open connections. At the beginning, we have broken the connection every hour, but the current solution is much more effective. Egon Disconnected from websocket - DelandeC - 2016-03-06 OK. What about not disconnecting logged in users (participants)? RE: Disconnected from websocket - Egon - 2016-03-06 You can switch it of by adding "?connect_onfocus=0" to the url. It is stored in a cookie. Look also what happens if a browser tab with a real-time map is closed, and opend one hour later. |