WICG/webpackage

Use-case: Service Worker cache population and synchronization

Open

#107 opened on Jan 10, 2018

View on GitHub
 (2 comments) (3 reactions) (0 assignees)Go (123 forks)github user discovery
feature requesthelp wanted

Repository metrics

Stars
 (1,256 stars)
PR merge metrics
 (PR metrics pending)

Description

If and when browser support for webpackage arrives, batch cache synchronization [1] or cache initialization [2] might be good use-cases, especially in the context of Service Worker. Using some sort of content negotiation mechanism, Service Worker might be able to ask the server for a webpackage that at least contains desired request URL(s). By unpacking the response and populating the cache, it can serve subsequent requests pretty quickly. What will be packed in the response is something that can be negotiated using some means or the server can decide as it does in case of HTTP/2 Server Hints (prefetch).

[1] https://github.com/WICG/BackgroundSync [2] https://developer.mozilla.org/en-US/docs/Web/API/Cache/addAll

Contributor guide

Research direction
Investigate how to use web packages for Service Worker cache population and synchronization, considering content negotiation and server hints.
Tech stack
javascriptgo
Domain
web dev
Issue type
Research
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
1
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
Under 1 hour
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
GitService WorkerCache API
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
75