Re: [ServiceWorker] Changing Request and fetch() (#625)

If the only difference this introduces is:

```js
var r = new Request('/');
fetch(r);
fetch(r);
```

…making the 2nd fetch fail, then this is fully compatible with how Chrome already behaves.

> Modifying a fetch on the go (e.g. changing priority).

+1 - I've already seen people expect adding headers to `fetchEvent.request` to work.

> Aborting a fetch.

What's the API proposal here? I thought it'd be a cancellable promise + cancellable stream? Neither of which seem to need changes to the current model (and would work with `fetch(str)`)

---
Reply to this email directly or view it on GitHub:
https://github.com/slightlyoff/ServiceWorker/issues/625#issuecomment-74508516