Basic service worker support (on-demand fixtures) with tests #9
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR covers the use of Service Workers for managing data through can-connect. Service workers are a new technology that allows caching, indexing, and manipulation of data outside the scope of a page, via an installable script.
Service workers operate significantly differently from Web workers in that:
For SPA creators, the service worker is likely to manage all or a large percentage of resources, especially when dealing with offline access. Having support for the service worker in can-connect allows CanJS to be used more effectively in apps where a service worker is used.
In addition to support for service workers, this PR includes a simple service worker that caches fixtures on demand. when a resource is fixturized via connection.fixturize(), the SW will manipulate the resources for GET/PUT/POST/DELETE itself, without passing the request on to the HTTP host.