- From: <piranna@gmail.com>
- Date: Mon, 25 Nov 2013 16:30:25 +0100
- To: Remi Grumeau <remi.grumeau@gmail.com>
- Cc: "public-webapps@w3.org" <public-webapps@w3.org>
> To be available offline, the device has to hit a server first, then the appcache "magic" happens. Obviously. > No reason the server couldn't prepare / select what to send to the device: iOS won't support WebM anytime soon, there is no reason to constantly ask iOS device the same info again & again. That just makes no sense, and force devs to produce device/os specific files (manifest) anyway. > > And it's not AppCache job to do so. Its job is just make a web document available offline + make updates simple & easy. > I'm not talking about remove the servers functionality, I only disagree with your statement about using only client-side technologies is bad, giving the impression that servers are necesary. Not today, they are necesary for bootstraping and access content on a reference place, but we should remove the idea of a "centralized web" as far as possible. AppCache here is a good tool for this, but here the server is only neccesary to generate the custom manifest file, no more, and also probably this manifest could be generated directly on client-side (don't know if it could be done with today technologies, but at least with ServiceWorkers it will be possible, and using them probably the AppCache manifest becames useless in this case of use). -- "Si quieres viajar alrededor del mundo y ser invitado a hablar en un monton de sitios diferentes, simplemente escribe un sistema operativo Unix." – Linus Tordvals, creador del sistema operativo Linux
Received on Monday, 25 November 2013 15:31:19 UTC