d0f94200e8
Motivation: We use the onStreamClosed(...) callback to return unconsumed bytes back to the window of the connection when needed. When this happens we will write a window update frame but not automatically call ctx.flush(). As the user has no insight into this it could in the worst case result in a "deadlock" as the frame is never written out ot the socket. Modifications: - If onStreamClosed(...) produces a window update frame call ctx.flush() - Add unit test Result: No stales possible due unflushed window update frames produced by onStreamClosed(...) when not all bytes were consumed before the stream was closed |
||
|---|---|---|
| .. | ||
| src | ||
| pom.xml | ||