View source for Gaia/Toolkit/Service Worker/Meetings/2015-04-16

Service worker Meet-up Notes


* B2G Vidyo room (Guest link: [http://j.mp/K03h7e) http://j.mp/K03h7e)]
* Thursdays at 18:00 CEST / 09:00 PDT
* Minutes copied to the wiki by host each week: [[Gaia/Toolkit/Service_Worker#What]]


04/16/2015<br />
=========


* New Gaia Architecture overview. How are we using sw
* 3 layers of cache:
** Render cache, to store data that is already preprocessed. i.e. html already built with SMS data for the SMS list view
** Custom cache: for customizing views. Allow partners or 3rd party devs to provide different UI experiences
** Offline cache: standard way to make an app work offline by allowing it to cache resources using the SW Cache API.


* Current state of sw
** Mostly working on Nightly
** Only works for https. There is a pref (dom.serviceWorkers.testing.enabled) to relax the security check.
** B2G issue regarding IPC security. Need a flag to workaround. Fix on the way (see {{bug|1125961#c35}} ).
** Most semantics and events are implemented (fetch, install, activate). Missing &quot;update&quot; ({{bug|1112469}} ). There are still issues with redirection.
** v1 ({{bug|1059784}} ) and v2 ({{bug|1131322}} ) metabugs based on priority
** app:// handler not implemented.
** Cannot use IDB in service workers yet {{bug|1137245}}
** Devtools
*** about:serviceworkers \o/ It shows installed and active service workers and allow to relaunch service workers
*** No way to see if a response comes from the service worker or the network yet (like in chrome)
*** Flag to allow insecure origins (http). SW work from localhost though
** Main target of DOM Core team is currently Nightly, not B2G. We need to help testing in B2G
** Push event on the way:
*** Core fixed {{bug|1038811}}
*** Pending B2G implementation {{bug|1151180}}
** Cache API (meta at {{bug|1110144)}}
*** Working on Nightly.
*** Also working on B2G. Main issue landed yesterday in m-c (bug 1151916).


* Thinks the team is going to focus:
** Performance:
*** how much time needs a sw to start?
*** time from a resource to be consumed from sw cache or http cache.
*** time from a resource in sw cache vs indexeddb resource.
*** Team in Taipei managed by Thinker also interested in review the performance of this service.
** Testing:
*** Platform unit testing disabled for B2G ({{bug|1056702)}}.
*** Try to test in the same environment sw run
** Library (libraries)
*** [https://github.com/arcturus/serviceworkerware https://github.com/arcturus/serviceworkerware]
*** An Express-like layer on top of ServiceWorkers to provide a way to easily plug functionality.
*** Middleware example and demo [https://github.com/arcturus/zipcacher https://github.com/arcturus/zipcacher]
** Shared worker/service worker coordination
*** For email want to talk to shared worker for service worker-initiated sync, working on that issue in: [https://github.com/slightlyoff/ServiceWorker/issues/678 https://github.com/slightlyoff/ServiceWorker/issues/678] &lt;- this will be really cool.


* Questions:
** How are we going to prepopulate caches?
*** This is something that we still need to figure out
** Does it make sense to prepopulate the render store?
*** Maybe not at build time but on background to do things like prerendering. It depends on app specific needs.