Issue metadata
Sign in to add a comment
|
BrowserProcess code should be able to share URLLoaderFactories |
||||||||||||||||||||||
Issue descriptionCurrently, central browser process objects only vend NetworkContexts, not URLLoaderFactories, so every consumer needs to create its own URLLoaderFactory before it can issue requests. We should have the central classes cache a URLLoaderFactory for use only by browser process consumers instead. We're probably fine not doing this for other interfaces, like the cookie store, though could be wrong about that.
,
Oct 3 2017
,
Oct 31 2017
The following revision refers to this bug: https://chromium.googlesource.com/chromium/src.git/+/6506f071492b4bd2a035c248d5e669474fb205f7 commit 6506f071492b4bd2a035c248d5e669474fb205f7 Author: John Abd-El-Malek <jam@chromium.org> Date: Tue Oct 31 15:09:49 2017 Use 0 to represent process_id of browser process when creating a URLLoaderFactory. This is per the NetworkContext::CreateURLLoaderFactory contract. BUG= 770854 Change-Id: I4ae9fb610d1860948c84fa9126e98d260afbdfbd Reviewed-on: https://chromium-review.googlesource.com/745161 Reviewed-by: Matt Menke <mmenke@chromium.org> Commit-Queue: John Abd-El-Malek <jam@chromium.org> Cr-Commit-Position: refs/heads/master@{#512832} [modify] https://crrev.com/6506f071492b4bd2a035c248d5e669474fb205f7/chrome/browser/net/system_network_context_manager.cc [modify] https://crrev.com/6506f071492b4bd2a035c248d5e669474fb205f7/content/browser/storage_partition_impl.cc
,
Nov 7 2017
Apologies, applied the wrong component in bulk. |
|||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||
Comment 1 by bugdroid1@chromium.org
, Oct 3 2017