| Summary: | [WK2][iOS] Fix build with !ENABLE(NETWORK_PROCESS) | ||||||
|---|---|---|---|---|---|---|---|
| Product: | WebKit | Reporter: | Chris Dumez <cdumez> | ||||
| Component: | WebKit2 | Assignee: | Chris Dumez <cdumez> | ||||
| Status: | RESOLVED WONTFIX | ||||||
| Severity: | Normal | CC: | andersca, ap, barraclough, cgarcia, commit-queue, koivisto, rniwa, sam | ||||
| Priority: | P2 | ||||||
| Version: | 528+ (Nightly build) | ||||||
| Hardware: | Unspecified | ||||||
| OS: | Unspecified | ||||||
| Attachments: |
|
||||||
|
Description
Chris Dumez
2015-07-10 10:53:44 PDT
Why do we need this working at all? (In reply to comment #1) > Why do we need this working at all? Maintaining this configuration is useful for testing purposes. For e.g., we are currently investigating a possible IPC perf regression. Created attachment 256594 [details]
Patch
(In reply to comment #2) > (In reply to comment #1) > > Why do we need this working at all? > > Maintaining this configuration is useful for testing purposes. For e.g., we > are currently investigating a possible IPC perf regression. From what? From enabling the Network Process? The non-network process configuration has never shipped on iOS. Hmm, there is a WebProcessPool::setUsesNetworkProcess() to do this at run time. At the moment, this is only exposed via a private C API but I guess this is enough for testing. It is likely that disabling NetworkProcess at runtime will change too much for being a useful testing tool. We won't use WebKit persistent cache, and I believe that CFNetwork cache is already broken on iOS due to some path/sandboxing confusion. |