This is hardly used anymore with the conversion of the code to work with network service. Now seems like a good time to get rid of it (it only has one method left, although it does seem to act as a key sometimes).
This is hardly used anymore with the conversion of the code to work with network service. Now seems like a good time to get rid of it (it only has one method left, although it does seem to act as a key sometimes).
Once the network service is the only code path that's used, then I suspect most of the code which runs on the IO thread can move to the UI thread. This would remove unnecessary thread hops (i.e. on navigations to talk to service worker and appcache code that lives on IO thread) and also simplify the code (e.g. to stop mirroring data for features on multiple threads, such as Instant or Extensions). We could then get rid of ResourceContext and ProfileIOData.
Comment 1 by jam@chromium.org
, Nov 27