Re: Request to summarize overall `state` of each spec

On 05 Nov 2013, at 13:53, Wonsuk Lee <wonsuk11.lee@samsung.com> wrote:

> Concerning to intro of ServiceWorker, I requested this to Alex couple of
> days ago. But I didn't receive his answer yet. So if he is not possible,
> could you or Kenneth explain this instead of him?

I think we can do an intro, if Alex is not available. However, would be great to get an update direct from Alex, Anne et al. during the meeting. Perhaps we can find additional Tue slot if that would work better?

Anyway, there’s some material in a written form already, so a useful intro might be to briefly look at:

1) How ServiceWorker is addressing the offline problem by allowing a web developer to programmatically intercept resource fetching and manage caching (a problem that was not adequately addressed by declarative AppCache due to limited expressiveness):

  https://github.com/slightlyoff/ServiceWorker/blob/master/explainer.md

This explainer in pretty detailed. However, it should be noted it only describes one kind of an event (“fetch”) that ServiceWorker could handle.

2) How to extend the model with new events beyond fetch for things like application lifecycle, alarms, push and system messages, inter-app communication etc. This is discussed e.g. in this gist (via [1]):

  https://gist.github.com/slightlyoff/7fae65a908ac318f69a3

Not as detailed as explainer around the fetch event, but gives you the basic idea of the extensibility of the model. Much of this is currently in scope for this group.

3) Should perhaps note and discuss that most (if not all?) of this is currently envisioned to work with the usual security model of the Web (the concept of origins, no up front permission grants etc).

4) Something else?

Thanks,

-Anssi

[1] https://github.com/slightlyoff/ServiceWorker/issues/79

Received on Tuesday, 5 November 2013 17:08:10 UTC