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

The main problem with "abort the request" vs "abort the signal" is that you don't really have a handle on a request (that might be an underlying problem I suppose). As was suggested elsewhere the fetch endpoint is really such that you pass it some callbacks and wait for those to be called. So if you want to cancel fetch you'd need to signal that in some way, likely through an object or a thing you already passed.

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