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

Also, [individual state events](https://github.com/stuartpb/FetchController-spec#fetchobserver-events) would be nice - *and* (if I understand @wanderview correctly) they would let the implementation dispatch fewer runnables.

> this would require dispatching many runnables back to the main thread.

Well, not necessarily. Like, one of the reasons I was describing *aggregating all state change into one callback* is that it would let many successive changes ride the same runnable. Also, we could have MutationObserver-style filters, so as to tell the network thread "you don't have to notify JS about anything but this one kind of change". (This would also be the same kind of filtering that'd be involved to implement individual-kind-of-state-arrival events, I think, no?)

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