RESOLVED FIXED 142821
[GTK][WK2] The WebKit network disk cache is not enabled
https://bugs.webkit.org/show_bug.cgi?id=142821
Summary [GTK][WK2] The WebKit network disk cache is not enabled
Marcos Chavarría Teijeiro (irc: chavaone)
Reported 2015-03-18 05:21:59 PDT
The http/tests/cache/disk-cache-validation.html layout test is failing on GTK+ since r179449 (http://trac.webkit.org/changeset/179449). This test enables the tests for cache funcionality. The output is the following: FAIL: Timed out waiting for notifyDone to be called
Attachments
Patch (2.53 KB, patch)
2015-05-05 03:05 PDT, Carlos Garcia Campos
mrobinson: review+
Chris Dumez
Comment 1 2015-03-23 14:18:06 PDT
*** Bug 141702 has been marked as a duplicate of this bug. ***
Chris Dumez
Comment 2 2015-03-23 14:18:24 PDT
*** Bug 141703 has been marked as a duplicate of this bug. ***
Chris Dumez
Comment 3 2015-03-23 14:18:47 PDT
*** Bug 142818 has been marked as a duplicate of this bug. ***
Chris Dumez
Comment 4 2015-03-23 14:20:39 PDT
Will consolidate the GTK TestExpectations via https://bugs.webkit.org/show_bug.cgi?id=142979.
Carlos Alberto Lopez Perez
Comment 5 2015-03-25 04:49:22 PDT
Mac has recently enabled NETWORK_CACHE (See bug 30322) by default on r179449 <ttp://trac.webkit.org/changeset/179449> Should GTK also enable it?
Carlos Garcia Campos
Comment 6 2015-03-25 04:53:06 PDT
(In reply to comment #5) > Mac has recently enabled NETWORK_CACHE (See bug 30322) by default on r179449 > <ttp://trac.webkit.org/changeset/179449> > > Should GTK also enable it? We first need to implement it :-) We also need to figure out what to do with the single web process model, I guess we could keep using the soup cache in the web process and the WebKit cache in the network process. Or we could make the single web process model become a multiple web process model with limit = 1, and the network process will always be used.
Michael Catanzaro
Comment 7 2015-03-25 05:36:28 PDT
(In reply to comment #6) > Or we could > make the single web process model become a multiple web process model with > limit = 1, and the network process will always be used. Note that a properly-sandboxed web process would not have any access to the network, so mandatory network process is something we'd come to eventually anyway. (Also, it would make Apple happy, but you know that.)
Zan Dobersek
Comment 8 2015-03-25 05:37:15 PDT
These are the slides from Antti's talk at the WK Contributors Meeting. https://trac.webkit.org/attachment/wiki/March%202015%20Meeting/Disk%20cache.pdf The main requirements are implementing NetworkCache::IOChannel and NetworkCache::Data. In GLib/GIO this might be possible by using GFile and GMemoryInputStream/GMemoryOutputStream (or whatever best replicates dispatch_io_* and dispatch_data_* APIs).
Michael Catanzaro
Comment 9 2015-03-25 07:36:42 PDT
(In reply to comment #6) > We first need to implement it :-) We also need to figure out what to do with > the single web process model, I guess we could keep using the soup cache in > the web process and the WebKit cache in the network process. Or we could > make the single web process model become a multiple web process model with > limit = 1, and the network process will always be used. Mandatory network process is something I would be willing to implement, for bug #140075.
Carlos Garcia Campos
Comment 10 2015-03-25 07:43:41 PDT
(In reply to comment #9) > (In reply to comment #6) > > We first need to implement it :-) We also need to figure out what to do with > > the single web process model, I guess we could keep using the soup cache in > > the web process and the WebKit cache in the network process. Or we could > > make the single web process model become a multiple web process model with > > limit = 1, and the network process will always be used. > > Mandatory network process is something I would be willing to implement, for > bug #140075. The question is whether sandboxing will be mandatory as well, or just optional. There are use cases in embedded world where network process, caches, and sandboxing are not needed at all.
Carlos Garcia Campos
Comment 11 2015-04-27 01:24:47 PDT
The initial implementation of the disk cache for soup landed in r183387. It works and all tests pass, but it hasn't been extensively tested yet. It can still be improved by using shareable resources, for example, but the only blocker is bug #144251 (to ensure all cache files are created with a creation time). So, I would like to enable the disk cache as soon as bug #144251 is fixed, so that we can start testing it now (early in the release cycle).
Carlos Garcia Campos
Comment 12 2015-05-05 03:05:01 PDT
Created attachment 252373 [details] Patch No more blockers, we are ready.
Martin Robinson
Comment 13 2015-05-05 07:39:55 PDT
Comment on attachment 252373 [details] Patch Nice.
Carlos Garcia Campos
Comment 14 2015-05-06 02:14:08 PDT
Note You need to log in before you can comment on or make changes to this bug.