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

@jan-ivar I have the feeling that the discussion of "Aborting a fetch" topic is always about something much more generic, such as cancelling a promise in general, or adding an aborting signal in general for everything in JavaScript.

But I think `fetch` is not at all general. It is so special that it needs low level work in JavaScript engine or binary library loaded.

All one needs to cancel a fetch are 2 things:
1. A reference to identify which fetch it is.
2. A function to cancel it.

Call it a controller with a method or whatever, they are essentially an identifier and an action.

I personally don't care whether the reference is a controller (object), numeric ID (int), promise(object) or a Web Worker (object). If I have to use a PID as control surface I'll use it.

Now thanks to the great hack @mitar mentioned, we have both 1 and 2.

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