>>>Hi,
>>>
>>>My ASP.NET web forms application is not a SPA application. So it has many pages. How would you suggest to use it when the browser does not have a good (or not at all) WiFi connection to the server? That is, the user may need to open page Page1.aspx, then Page2.aspx, and so on, jumping from one to another. (I have an idea/scope of what to do with the data from another thread). But what about the pages? Do they have to be stored in the local storage too?
>>>
>>>TIA
>>
>>I was going to suggest using offline manifests (which basically cache a supplied list of pages for use offline) but I suddenly see this is being deprecated which seems rather odd..
>>
>>The suggested alternative is apparently 'Service Workers' which I know nothing about - not even sure whether any browsers support it yet. My guess is that, in practice application cache will be around for quite a while (it's on all current HTML5 browsers.
>>
>>See: https://developer.mozilla.org/en-US/docs/Web/HTML/Using_the_application_cache
>>
>>I'm going to read what I can on Service Workers and will let you know if I'm any the wiser :-}
>
>Thank you very much.

So far I've seen that it's assumed that application cache will be around for a while (i.e. years) and, OTOH, Service workers are currently only on Chrome, Firefox and Opera

https://developer.mozilla.org/en-US/docs/Web/API/Service_Worker_API/Using_Service_Workers#Browser_compatibility