New issue
Advanced search Search tips

Issue 805986 link

Starred by 3 users

Issue metadata

Status: Available
Owner: ----
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 3
Type: Feature
Proj-Servicification

Blocking:
issue 598073



Sign in to add a comment

Add a per-RenderFrameHost sidechannel to the NetworkService.

Project Member Reported by mmenke@chromium.org, Jan 25 2018

Issue description

This 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.
 
Blocking: 598073
Owner: ----
Status: Available (was: Assigned)
Going to punt on this for now - getting too much pushback, and don't want to land a design I'm not happy with.

Comment 2 by dxie@chromium.org, May 15 2018

Owner: mmenke@chromium.org
Status: Assigned (was: Available)
hi matt, let me know if this is needed for the initial launch of network services.

Comment 3 by mmenke@chromium.org, May 15 2018

Owner: ----
Status: Available (was: Assigned)
It's not strictly necessary, it just adds a ton of technical debt not to do this sooner rather than later.

Comment 4 by dxie@chromium.org, May 22 2018

Labels: Hotlist-KnownIssue

Sign in to add a comment