Interesting point in case for service workers. I think I'm ignorant about the technology and being in QA, I tend to play the devil's advocate. Don't get me wrong, I do wish for what you're stating. I am concerned about throwing things over the wall to service workers; I get the feeling we'll still run into challenges to confront offline cases.
An edge case example of what I'm worried about is: Camping and being in the middle of no where, and then the phone dies. You're able to charge the device via Pan Charger ( http://www.slashgear.com/pan-charger-boils-your-iphone-battery-back-to-life-21160661/ ) or some similar device. Will the service worker still be able to launch the dialer for emergency calls without having a net connection? I guess my assumption here is that the service worker relies on information in cache and being active. What happens when that gets disrupted? I'm trying to read up on it a little here : http://www.w3.org/TR/service-workers/ Regards, Naoki On Jan 30, 2015, at 11:08 AM, Benjamin Francis <[email protected]> wrote: > On 30 January 2015 at 18:54, Naoki Hirata <[email protected]> wrote: > I have to agree with Kevin. My biggest concerns are for performance, offline > cases, and issues with caching with full hosted apps. > > As Dale says this is exactly why we need Service Workers. I'm not suggesting > that all apps should require an Internet connection all the time, that would > never work :) > > Currently people are creating packaged apps so that their apps work offline. > But I would argue that packaged apps miss out on most of the benefits of the > web. _______________________________________________ dev-webapps mailing list [email protected] https://lists.mozilla.org/listinfo/dev-webapps
