Re: [whatwg/fetch] Request body streams should use chunked encoding (#966)

I see.

I think the complexity of the H/2 path is overstated, and unreasonably
biased towards presumed server-side complexity, while overlooking the
client-side complexity (that is, complexity for the JS developer primarily,
although to a much lesser extent the UA developer as well).

Having an API that only works over H/2, which does not require the
complexities previously described and deterministically fails fast, seems a
much better developer experience than a non-deterministic API that
heuristically encounters issues. That seems like a much more useful
starting point, and provides a forward path to allowing developers to get
determinism by default, and opt-in to non-determinism if they’d like to try
to handle it. That would seem to allow shipping something to users sooner,
and that works more reliably, then trying to optimize for a single server
implementor.


-- 
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/966#issuecomment-586940793