Norman Maurer a469c2eaac Don't propagate Http2WindowUpdateFrame to the child channel / propagate Http2ResetFrame as user event when using Http2MultiplexHandler (#9290) ... Motivation: We should not propage Http2WindowUpdateFrames to the child channels at all as these are not really use-ful and should not be flow-controlled via `read()` anyway. In the other hand Http2ResetFrame is very useful but should be propagated via an user event so the user is aware of it directly even if the user stops reading. Modifications: - Dont propagate Http2WindowUpdateFrames when using Http2MultiplexHandler - Use user event for Http2ResetFrame when using Http2MultiplexHandler - Adjust javadoc of Http2MultiplexHandler - Add unit tests Result: Fixes https://github.com/netty/netty/pull/8889 and https://github.com/netty/netty/pull/7635		2019-06-27 21:53:15 +02:00
..
src	Don't propagate Http2WindowUpdateFrame to the child channel / propagate Http2ResetFrame as user event when using Http2MultiplexHandler (#9290)	2019-06-27 21:53:15 +02:00
pom.xml	Remove duplicated declaration of dependency	2019-01-21 11:54:55 +01:00