Issue metadata
Sign in to add a comment
|
Add a per-RenderFrameHost sidechannel to the NetworkService. |
||||||||||||||||||||
Issue descriptionThis will allow NetworkService data we don't trust to send through the renderer process to be sent directly to the browser process, with per-RenderFrameHost logic for how to respond (Like for handling auth). Currently, there's a global NetworkServiceClient for this purpose, but since it's at global scope, it relies on process IDs and renderer IDs, which is something the network service shouldn't know about.
,
May 15 2018
hi matt, let me know if this is needed for the initial launch of network services.
,
May 15 2018
It's not strictly necessary, it just adds a ton of technical debt not to do this sooner rather than later.
,
May 22 2018
|
|||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||
Comment 1 by mmenke@chromium.org
, Feb 8 2018Owner: ----
Status: Available (was: Assigned)