Re: [whatwg/fetch] Aborting a settled request (and why abort should be synchronous) (#448)

The problem with synchronous is that "a fetch" isn't necessarily on the same thread as JavaScript. So I guess you could keep some local state, but there's some state propagation that needs to happen. This becomes more problematic if we ever introduce request coalescing.

And then there's the question of whether such propagation happens when a service worker takes over a request from a fetch (which results in a nested fetch of sorts).

-- 
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/448#issuecomment-270606993