The new preconnect predictor should use the network service.
For instance, it should not rely use the ResourceDispatcherHost (unsupported by the network service) but the WebContentsObserver interface and the NavigationHandle, which will have to be augmented with any capacity required and not yet provided.
I'm still blocked on https://crbug.com/850066 . I'd be much easier for me to switch to the preconnect and the preresolve Network Service API at the same time.
alexilin: The HostResolver API just landed, though it has no consumers yet. See NetworkContext::ResolveHost. There's another CL out which allows creating host resolver objects which can be used off the main thread, if you need to do stuff on the IO thread still (Though without any network stuff on the IO thread, that's probably not necessary)
There are still a bunch of PredictorBrowserTest tests listed in testing/buildbot/filters/mojo.fyi.network_browser_tests.filter. Are these for the old implementation? Can we just early out in those tests if network service is enabled?
Comment 1 by bugdroid1@chromium.org
, Mar 12 2018