Norman Maurer 307efbe49c Split multiplexing from frame decoding to allow easier customization of frame processing and better seperation of responsibilities (#9239) ... Motivation: In the past we had the following class hierarchy: Http2ConnectionHandler --- Http2FrameCodec -- Http2MultiplexCodec This hierarchy makes it impossible to plug in any code that would like to act on Http2Frame and Http2StreamFrame which can be quite useful for various situations (like metrics, logging etc). Beside this it also made the implementtion very hacky. To allow easier maintainance and also allow more flexible costumizations we should split Http2MultiplexCodec and Http2FrameCode. Modifications: - Introduce Http2MultiplexHandler (which is a replacement for Http2MultiplexCodec when used together with Http2FrameCodec) - Mark Http2MultiplexCodecBuilder and Http2MultiplexCodec as deprecated. People should use Http2FrameCodecBuilder / Http2FrameCodec together with Http2MultiplexHandlder in the future - Adjust / Add tests - Adjust examples Result: More flexible usage possible and less hacky / coupled implementation for http2 multiplexing		2019-06-24 09:17:15 +02:00
..
java/io/netty/example	Split multiplexing from frame decoding to allow easier customization of frame processing and better seperation of responsibilities (#9239)	2019-06-24 09:17:15 +02:00
resources	fix the typos	2017-04-20 04:56:09 +02:00