Re: [whatwg/fetch] WIP: Cancelation (#523)

Hmm, that doesn't seem to work so great. I'd expect reading a chunk or transmitting _bs_ to be interruptible, whereas that doesn't seem possible with that spec.

Maybe we could start by listing all the places you anticipate being able to abort? Off the top of my head:

- Before taking any action
- During "transmit body"
  - During reading a chunk
  - During transmitting a chunk
  - Before reading the next chunk
- During service worker handling
- During foreign fetch handling
- During HTTP-network fetch's
  - During "making a HTTP request" (i.e. the step that gets the headers)
  - During the body byte receive loop
- All of the above, but during a CORS preflight fetch

It looks to me like several of these already have provisions for the fetch being terminated during them. IMO we should just make sure to handle the rest, and then make the abort steps terminate the fetch.

-- 
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/pull/523#issuecomment-307182760