To remove the network service from the browser process, all communication with other services needs to be switched to mojo. This bug tracks the efforts to do this for the Chrome Data Reduction Proxy.
Discussed with bengr@ today: We do not think there is a need to block OS-Windows network servicification on canary channel behind DRP mojofication. However, we need to resolve this bug (or figure out an alternate path) before network servicification happens for other platforms or channels where DRP user population is more significant.
I've filed issue 855620 to track migrating DRP to network::SimpleURLLoader and issue 855621 to track temporarily disabling DRP when the Network Service is enabled to avoid these sharp edges.
cduvall@ will be taking over this work. There are two in-progress patches I have from this issue:
network_delegate_proxy_delegate_merge.patch attempts to merge ProxyDelegate into NetworkDelegate in order to allow proxy decisions to be made on a per-URLRequest level rather than through a ProxyDelegate which is assigned to a network context and doesn't get passed the URLRequest.
This patch broke the DataReductionProxyNetworkDelegate tests and so the smaller patch proxy_delegate_in_network_delegate_tests.patch just adds a DataReductionProxyDelegate to these tests in order to resolve the failures separately from the larger merge.
I'm marking this tracking bug as fixed, since all browser tests are passing for DRP in network service. We can create more targeted bugs for any remaining network service DRP functionality/metrics that are remaining.
Comment 1 by rdsmith@chromium.org
, May 11 2017