Re: HTTP/2 response completed before its request

Cool! So this is a normal case.

One corner case of a corner case is if the server's early response has more
than a window's worth of data...

Our client wouldn't acknowledge that data because it doesn't start reading
until it's done writing.

And if the server writes its early response before discarding/resetting the
request, that write might stall waiting for a WINDOW_UPDATE that won't ever
come. Deadlock!

(This is probably just a theoretical problem!)