If you don’t want to store anything on the server, why serve the static JS and HTML? You can embed them in the URL also.
In that cass the URL just becomes a local file.
You should store the file locally, along with all the data it embeds.
Or you can store the files on a CDN at the edge. The problem with the latter is that people can abuse the storage.
Really, the Web needs to be overhauled to have a topology more like a DHT, where you only have peering agreements with a few peers, and they cache the content temporarily when it is requested a lot. So no centralized servers at all.
If you don’t want to store anything on the server, why serve the static JS and HTML? You can embed them in the URL also.
In that cass the URL just becomes a local file.
You should store the file locally, along with all the data it embeds.
Or you can store the files on a CDN at the edge. The problem with the latter is that people can abuse the storage.
Really, the Web needs to be overhauled to have a topology more like a DHT, where you only have peering agreements with a few peers, and they cache the content temporarily when it is requested a lot. So no centralized servers at all.