New issue
Advanced search Search tips
Note: Color blocks (like █ or █) mean that a user may not be available. Tooltip shows the reason.

Issue 694778 link

Starred by 2 users
Status: WontFix
Owner:
lafo...@chromium.org
Closed: Apr 2017
Cc:
█ cbentzel@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: ----
Type: ----



Sign in to add a comment

[Component Request] Internals>Precache

Project Member Reported by twif...@chromium.org, Feb 21 2017 
1] Component Name: Precache

2] Parent Component (e.g. Blink, UI>Browser, etc...): Internals

3] Description of Component: Efforts to precache static subresources for the purposes of speeding up content loading.

For the bug reviewer, not the component description: Current projects include Bork (//components/precache) and Speculative Prefetch.

4] Admin/ Owner: twifkak, mattcary

5] Please specify what triage practices will be followed for the component.

Likely none, or "heroic" triage only. I don't expect many end-users reports for this, so it'll be up to the maintainers of the projects that make up this component.

Comment 1 by laforge@google.com, Feb 28 2017 

Should this live under Internals>Network?

Comment 2 by twif...@chromium.org, Feb 28 2017 

Yes, that works. The code lives outside the network stack, and includes some non-network stuff like Java code to schedule background tasks. But ultimately it's an invisible thing meant to improve perceived network performance.

Comment 3 by lafo...@chromium.org, Mar 6 2017

Cc: cbentzel@chromium.org
Hey Chris,

Any objections if we parent Precache under Internals>Network (i.e. Internals>Network>Precache)?

Comment 4 by cbentzel@chromium.org, Mar 6 2017 

Internals>Preload likely a better place.

Comment 5 by lafo...@chromium.org, Apr 11 2017

Owner: lafo...@chromium.org
Status: WontFix (was: Untriaged)
Closing this out based on Chris's feedback.  Please re-open if we need to reconsider.
►

Sign in to add a comment