Welcome! This forum has a treasure trove of great info – Scouters helping Scouters! Just a heads up, though - all content, information, and opinions shared on this forum are those of the author, not the BSA.
Why does the page code of Scoutbook force the end user to refresh a page (typically when they are in the middle of something that they’ve already done several mouse click selections that they then have to redo again after a refresh. This is scripting languages. There are ways for the developers to force the browser to not load from the cache (and request the latest from the scoutbook servers) in one line of javascript. This is way more effecient and keeps the end user from having to redo something on the site constantly.
I am in Scoutbook/Scoutbook+ daily and see it a few times a week at least. My point is if this were coded using scripting language best practices an end user should never be prompted to refresh.
Scoutbook Plus is broken into “chunks” of code using Code Splitting | webpack When a module is updated, the update is fetched but does not become active until the user refreshes the page. The refresh pop-up is to alert the user that this needs to be done to get the latest code.
So then why not have every page in Scoutbook set to never cache. That way the end user will always get new code when they go to a page and they won’t see the popup unless they’ve had the page open while new code is deployed?
Because that puts too much load on the servers. Remember a few years ago when Scoutbook melted down on Monday nights because too much load? One of the ways performance was improved was by taking advantage of the cache, thus reducing server load.
