- From: <piranna@gmail.com>
- Date: Mon, 25 Nov 2013 19:58:47 +0100
- To: James Greene <james.m.greene@gmail.com>
- Cc: Remi Grumeau <remi.grumeau@gmail.com>, "public-webapps@w3.org" <public-webapps@w3.org>
> 1. I'm not advocating for full scriptability, just basic support detection,
> e.g.:
> `if accepts("audio/ogg") ...`
>
Some kind of basic "scriptability" like the one on CSS, isn't it? Ok, it's good.
> The main problem I'd see there is if the browser also needs to know what
> plugins
> (or even JS libs, I suppose) are capable of consuming.
>
More or less why I was going down the full Javascript path :-)
> 2. AFAIK, using ServiceWorkers requires that the resources are
> programmatically
> fetched by the ServiceWorker. This is different than a manifest which is
> capable
> of figuring the cache out on the fly as resources are loaded.
>
Not really, ServiceWorker doesn't mandate that all resources go though
it, but it's being showed as the main use case (not mine, I want to
combine it with ProtocolHandler to create my own protocols and manage
them on client-side...).
> I'm not opposed to just punted and saying that ServiceWorker is the way to
> deal
> with this, though. I have no personal use cases at the moment for this
> functionality... just playing devil's advocate for the OP. :)
>
Lol! Ok :-)
--
"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 18:59:34 UTC