|
|
|
|
|
|
by galaxyLogic
1946 days ago
|
|
|
I leave the browser waiting for a fetch-response from the server. The server responds only later when the page that is open in the browser was updated on server. Seems to work much of the time, but sometimes it seems Chrome closes the connection after a timeout and shows a network error in the dev-tools. FireFox not. I assume web-sockets could make it work more robustly. |
|
|