Scott Mitchell 2d10b252f9 HTTP/2 Inbound Flow Control Connection Window Issues ... Motivation: The inbound flow control code was returning too many bytes to the connection window. This was resulting in GO_AWAYs being generated by peers with the error code indicating a flow control issue. Bytes were being returned to the connection window before the call to returnProcessedBytes. All of the state representing the connection window was not updated when a local settings event occurred. Modifications: The DefaultHttp2InboundFlowController will be updated to correct the above defects. The unit tests will be updated to reflect the changes. Result: Inbound flow control algorithm does not cause peers to send flow control errors for the above mentioned cases.		2014-12-04 14:10:11 -05:00
..
src	HTTP/2 Inbound Flow Control Connection Window Issues	2014-12-04 14:10:11 -05:00
pom.xml	Fix dependency issues with hamcrest	2014-12-04 17:53:35 +09:00