You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Feb 17, 2024. It is now read-only.
Is your feature request related to a problem? Please describe.
The map data is currently fetched by each client in the form of individual HTTP Get requests several times per second. This clutters up the network request log in the browser and also is not a very clean way of implementing constantly changing data.
Describe the solution you'd like
Sending the data via persistent websockets using Channels would be a cleaner way to get the map data from the server to the client. It would also allow for continuously updating maps, rather than maps that update every x milliseconds (based on the setInterval() parameters for the AJAX request.)
Describe alternatives you've considered
The alternative would be the current solution, which involves each client polling the server every x milliseconds for new map data.
The text was updated successfully, but these errors were encountered:
Is your feature request related to a problem? Please describe.
The map data is currently fetched by each client in the form of individual HTTP Get requests several times per second. This clutters up the network request log in the browser and also is not a very clean way of implementing constantly changing data.
Describe the solution you'd like
Sending the data via persistent websockets using Channels would be a cleaner way to get the map data from the server to the client. It would also allow for continuously updating maps, rather than maps that update every x milliseconds (based on the setInterval() parameters for the AJAX request.)
Describe alternatives you've considered
The alternative would be the current solution, which involves each client polling the server every x milliseconds for new map data.
The text was updated successfully, but these errors were encountered: