Bug 213367
| Summary: | WKURLSchemeHandler does not fully implement the Http cache protocol | ||
|---|---|---|---|
| Product: | WebKit | Reporter: | mali <ak4868> |
| Component: | WebKit2 | Assignee: | Nobody <webkit-unassigned> |
| Status: | RESOLVED WONTFIX | ||
| Severity: | Normal | CC: | achristensen, beidson, webkit-bug-importer |
| Priority: | P2 | Keywords: | InRadar |
| Version: | Other | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
mali
The current implementation of WKURLSchemeHandler only has the memory cache of http resources and no disk cache. Can the requests processed by WKURLSchemeHandler fully implement the entire Http cache protocol. WKURLSchemeHandler requires cross-process communication. If there is a disk cache, the kernel can avoid many unnecessary Cross-process data transfer to improve performance
| Attachments | ||
|---|---|---|
| Add attachment proposed patch, testcase, etc. |
Radar WebKit Bug Importer
<rdar://problem/64550318>
Alex Christensen
The whole point of WKURLSchemeHandler is that it is not HTTP. If you want HTTP-like caching, you will have to implement it yourself. It wouldn't save any Cross-process data transfers if we did because WebKit uses the network process for the HTTP disk cache.
mali
Sorry what I mean may not be in place. WKURLSchemeHandler is processed on the process of each WKWebView instance. When this process exits, the memory cache associated with it is destroyed. In other cases, WKWebView will create a Persistent network process for WKProcessPool, at this time these cache objects will not be destroyed as the WKWebView instance exits, is this more reasonable?