Ehsan at 22:30, 14 July 2015

2015-07-14T22:30:07Z

← Older revision		Revision as of 22:30, 14 July 2015
Line 1:		Line 1:
	This is a proposal for allowing usage of service workers without installing them. This will be useful for APIs such as Push, and Background Sync. FetchEvent will not be dispatched to such service workers.		This is a proposal for allowing usage of service workers without installing them. This will be useful for APIs such as Push, and Background Sync. FetchEvent will not be dispatched to such service workers. The script source for these service workers wouldn't be cached locally (except for perhaps in the HTTP cache as all other resources) so every time that the UA wants to spin up one of these, it needs to potentially load it from the network.

	== Changes to Service Workers ==		== Changes to Service Workers ==

Ehsan: Created page with "This is a proposal for allowing usage of service workers without installing them. This will be useful for APIs such as Push, and Background Sync. FetchEvent will not be disp..."

2015-07-14T18:01:11Z

Created page with "This is a proposal for allowing usage of service workers without installing them. This will be useful for APIs such as Push, and Background Sync. FetchEvent will not be disp..."

New page

This is a proposal for allowing usage of service workers without installing them. This will be useful for APIs such as Push, and Background Sync. FetchEvent will not be dispatched to such service workers.

== Changes to Service Workers ==

The RegistrationOptions dictionary would need to be extended like this:

<pre>dictionary RegistrationOptions {
USVString scope;
boolean install;
};</pre>

The [http://slightlyoff.github.io/ServiceWorker/spec/service_worker/index.html#register-algorithm Register algorithm] would need to be modified around step 4.2 to treat install: false specially by not doing nothing when an existing worker has been installed for that scope (and maybe reusing it, that requires more thought) and skip running the [http://slightlyoff.github.io/ServiceWorker/spec/service_worker/index.html#update-algorithm Update algorithm].

Furthermore, the current definition of [http://slightlyoff.github.io/ServiceWorker/spec/service_worker/index.html#dfn-service-worker-registration registrations] heavily depends on the workers being installed, and we would need to perhaps have a parallel list of workers that have been registered in this new mode. We need to figure out how to treat the intersection of these two sets.

We can probably expose a new readonly boolean attribute on ServiceWorkerRegistration like installed to be able to return a ServiceWorkerRegistration object from register() for the install: false case that will have slightly different semantics (such as never having an installing and waiting worker, its update() method not doing anything, else) but this will have the nice property that the [https://w3c.github.io/push-api/#extensions-to-the-serviceworkerregistration-interface Push API hooks] and the similar can work with both types of workers.

Install-less Service Workers - Revision history

Ehsan at 22:30, 14 July 2015

Ehsan: Created page with "This is a proposal for allowing usage of service workers without installing them. This will be useful for APIs such as Push, and Background Sync. FetchEvent will not be disp..."