Skip to content
This repository has been archived by the owner on Jun 30, 2023. It is now read-only.

Add "Implementation Considerations" section #31

Closed
igrigorik opened this issue May 4, 2015 · 3 comments
Closed

Add "Implementation Considerations" section #31

igrigorik opened this issue May 4, 2015 · 3 comments
Assignees
@igrigorik
Milestone
Level 1

Comments

@igrigorik
Copy link
Member

@igrigorik igrigorik mentioned this issue May 4, 2015
Closed
@sleevi
Copy link

sleevi commented Jul 17, 2015

Also want to discuss dns-prefetch (added from Issue #37 ) and the privacy implications regarding it. For example, see https://www.chromium.org/developers/design-documents/dns-prefetching for some of the discussion.

@igrigorik
Copy link
Member Author

Matching should probably preload's cache definition and algorithm. Blocked on: w3c/preload#30

@igrigorik igrigorik added this to the Level 1 milestone Jun 29, 2016
@igrigorik igrigorik self-assigned this Jun 29, 2016
@ithinkihaveacat ithinkihaveacat mentioned this issue Sep 17, 2016
Closed
@yoavweiss
Copy link
Contributor

Getting back to this after many many years...
w3c/preload#30 is actually being defined and should land shortly.
For the rest, #86 seems more specific, so closing this one.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees

@igrigorik igrigorik

Labels
None yet
Projects
None yet
Milestone
Level 1
Development

No branches or pull requests
3 participants
@igrigorik @yoavweiss @sleevi