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
There is now a lag of ~ 4 secs on opening LCC's consultation map. This is mainly due to the large number of AJAX calls to the Cyclescape server (about 70 of them) to get the issues for TfL and each borough:
Possible actions:
batch up the AJAX calls to the CyclesScape API
** E.g. could do this with a single call getting all the issues in Greater London, then sorting them on the client side.
** a solution where the server does most of the sorting work would be better (simpler and more responsive).
Minify the scripts
The text was updated successfully, but these errors were encountered:
** a solution where the server does most of the sorting work would be better (simpler and more responsive).
Write a spec and ask Nikolai to implement it in the API.
There is now a lag of ~ 4 secs on opening LCC's consultation map. This is mainly due to the large number of AJAX calls to the Cyclescape server (about 70 of them) to get the issues for TfL and each borough:
Possible actions:
** E.g. could do this with a single call getting all the issues in Greater London, then sorting them on the client side.
** a solution where the server does most of the sorting work would be better (simpler and more responsive).
The text was updated successfully, but these errors were encountered: