Re: [whatwg/fetch] Fetch body streams are not full duplex (#1254)

So what API changes would we make here and how are they observable in half-duplex implementations? Would we end up with hanging promises? (I don't think the upload stream racing with the response headers would be a good forward-looking design. You don't want to depend on that with regards to forwarding the error.)

Is that all we'd need to change? Is that a change we can make? I suspect you can already run into this scenario with blobs and I/O errors, for instance.

I think it's worth exploring this a bit, but if it turns out the existing API has half-duplex baked in already than @yutakahirano's suggestion of a _fullDuplex_ opt-in seems like the way to go. And we could make that throw today so it'll be forward-compatible a couple years from now.

-- 
Reply to this email directly or view it on GitHub:
https://github.com/whatwg/fetch/issues/1254#issuecomment-1154136124
You are receiving this because you are subscribed to this thread.

Message ID: <whatwg/fetch/issues/1254/1154136124@github.com>