Change Details

In order to run service-worker code on the server, we'll need to provide [the interfaces](http://www.w3.org/TR/service-workers/) available in the browser: - Registration to a scope. This introduces a very basic routing scope, but most finer-grained routing is likely to happen inside the service worker. - [fetch](https://fetch.spec.whatwg.org), possibly via https://github.com/matthew-andrews/isomorphic-fetch - This also provides a basic `Response` implementation, wrapping the node HTTP response object. - `Request` wrapper for Node's [ClientRequest](https://nodejs.org/api/http.html#http_class_http_clientrequest). - [Cache](http://www.w3.org/TR/service-workers/#cache-objects). On the server, we might want to use this for in-process caching of frequently-used fragments.

In order to run service-worker code on the server, we'll need to provide [the interfaces](http://www.w3.org/TR/service-workers/) available in the browser: - Registration to a scope. This introduces a very basic routing scope, but most finer-grained routing is likely to happen inside the service worker. - [fetch](https://fetch.spec.whatwg.org), possibly via https://github.com/matthew-andrews/isomorphic-fetch - This also provides a basic `Response` implementation, wrapping the node HTTP response object. - `Request` wrapper for Node's [IncomingMessage](https://nodejs.org/api/http.html#http_http_incomingmessage). - [Cache](http://www.w3.org/TR/service-workers/#cache-objects). On the server, we might want to use this for in-process caching of frequently-used fragments.

In order to run service-worker code on the server, we'll need to provide [the interfaces](http://www.w3.org/TR/service-workers/) available in the browser: - Registration to a scope. This introduces a very basic routing scope, but most finer-grained routing is likely to happen inside the service worker. - [fetch](https://fetch.spec.whatwg.org), possibly via https://github.com/matthew-andrews/isomorphic-fetch - This also provides a basic `Response` implementation, wrapping the node HTTP response object. - `Request` wrapper for Node's [ClientRequestIncomingMessage](https://nodejs.org/api/http.html#http_class_http_clientrequestincomingmessage). - [Cache](http://www.w3.org/TR/service-workers/#cache-objects). On the server, we might want to use this for in-process caching of frequently-used fragments.