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

>From an implementation perspective a simple "check a cancel flag" is not quite adequate.  There are places where you can be waiting for external input (connecting a socket, etc) and not performing any kind of active local code.  In these cases we would pro-actively take action to cancel like closing the socket instead of checking a flag.

I'm not sure if we really need to capture that kind of thing in the spec or not.

Talking with @annevk it sounds like we could probably immediately mark the DOM side of the fetch operation dead immediately.  There is probably no need to wait for the cancel operation to completely close the socket.  (Or is there?)

-- 
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-311735360