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

Commenting to illustrate need:

I have a direct need for this as well. Working on a private code base, but the use case is we have a lot of streaming that we're currently multiplexing over a WebSocket. Most of these streams are simply "1 request, N responses", however 2 or 3 of them are bidirectional. Moving to http/2 for "1 request, N responses" case would be a boon for us, because we'd be able to let http/2 do the multiplexing for us, less JavaScript, less code running on the server and the client (because there's no need to wrap something in an "envelope" and match it up on both sides). The lack of bidirectional communication (full duplex) in fetch is really the only thing holding me up from moving everything over to http/2.

There's always `WebTransport` of course, but I feel like http/3 is an even taller order, I don't think it's supported in Node yet, and it's unlikely that the support is great in other languages our teams deal with.

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

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