Re: [whatwg/fetch] Aborting a fetch: The Next Generation (#447)

I still dislike mutating the Request with state like cancelation, etc, but I'm willing to accept it at this time.  I just wish we had an object that represents the on-going fetch activity.  Request is more "a fetch that can be performed" and a Response is "a fetch that has been performed".

If we go with `Request.cancel()`, please include a `Request.cancelled` getter determining the current state as well.

Also, should we allow script to tell if a Request is completed and `cancel()` will effectively be a no-op?

> Service workers shouldn't have control over incoming requests.

I'm not sure I understand this assertion.  The entire ServiceWorker interception system is to allow it to gain some control over how that incoming request is processed.

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/whatwg/fetch/issues/447#issuecomment-270442922