Content Modularization Project: Service Worker |
|||||||||||||||
Issue descriptionTracking bug for the service worker part of the Content Modularization Project. Some task items: -convert existing IPCs to mojo -consume quota/blob/leveldb through their new mojo interface -change how it hooks into network layer by implementing new mojo interfaces (to be spec’d, see bug 611897 ) -move browser-side code from content/browser/service_worker to components/service_worker per intent to get rid of content -separate from rest of browser code so that it can eventually run in the profile process (no reason for it to run unsandboxed)
,
May 16 2016
,
May 16 2016
,
May 16 2016
,
May 17 2016
btw above is for the content/browser code. The code in content/renderer should move to blink per onion soup project.
,
May 26 2016
,
Aug 31 2016
,
Feb 16 2017
From internal discussion: * we might also want to consider if it's possible to move the request intercepting part from //net to Blink, that way we could possibly remove one extra inter-process hops. (Need more investigation to see if it's really possible)
,
Feb 21 2017
,
Apr 26 2017
,
Apr 28 2017
Assigning this to me.
,
Jul 25 2017
,
Jul 25 2017
,
Aug 4 2017
,
Aug 4 2017
,
Nov 7 2017
Appending component Internals>Services to S13N projects and changing the Type (for tracking sake) to Type=Task.
,
Jan 15
Our thinking of what it means to modularize content has changed since this was filed. Bug 715640 tracked rewriting the SW networking glue and is launched already. I don't see much benefit to move SW outside of content/browser at this point. |
|||||||||||||||
►
Sign in to add a comment |
|||||||||||||||
Comment 1 by jam@chromium.org
, May 16 2016