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

> @blesh to clarify, it should be clear from #447 (comment) that the usage of the fetch API without a wrapper is heavily guiding the design here.

@jakearchibald anyone that wants composition with cancellation will _definitely_ need to wrap fetch with this design. Since the future to the result is not linked to that which can abort the future in any way, there's no way to return both together from any function as a single object unless they're combined via some common wrapper into a more composable shape, refCounting is added, etc. For reactive programming, this will be a huge bummer. Perhaps there is a misunderstanding of how it could be implemented with ref counting? I don't know.

Outside of that, I think this design is very unergonomic and unlike anything I've seen in the ecosystem. I understand the controller is for cancellation, but at first blush I have no idea what a "fetchObserver" is (I presume it's a reference to a single subscriber to the fetch resulting promise? It's what it sounds like. and wouldn't you have more that one?) But that's anecdotal and totally subjective.



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