cours #114

New issue

Open

opened 2025-07-22 21:11:36 +02:00 by Anri · 2 comments

Anri commented

2025-07-22 21:11:36 +02:00

Owner

instead of sending everypage the json of the filetree, use a api call from js to the backend to retrieves it

in either case, the JS is needed to render the filetree, so using the api will allow:

a lighter html (even if we are using brotli to compress the html), so a faster load

refactoring that will not changes the data type of the json so it should not be too much work

instead of sending everypage the json of the filetree, use a api call from js to the backend to retrieves it in either case, the JS is needed to render the filetree, so using the api will allow: - a lighter html (even if we are using brotli to compress the html), so a faster load refactoring that will not changes the data type of the json so it should not be too much work

Anri commented

2025-07-29 00:13:02 +02:00

Author

Owner

i have tested with and without the filetree, i win one BIG second of load on EACH page

I have not looked yet if the second is in the Rust side, or in the internet download side (probably not), or in the JS side (probably that)

If its JS, we could look into loading the file tree in an asynchronous way so it doesnt "lock" the page during a second

i have tested with and without the filetree, i win one BIG second of load on EACH page I have not looked yet if the second is in the Rust side, or in the internet download side (probably not), or in the JS side (probably that) If its JS, we could look into loading the file tree in an asynchronous way so it doesnt "lock" the page during a second