netty5/transport
Norman Maurer a729e0fcd9 Decouple DefaultChannelPipeline from AbstractChannel
Motivation:

DefaultChannelPipeline was tightly coupled to AbstractChannel which is not really needed.

Modifications:

Move logic of calling handlerAdded(...) for handlers that were added before the Channel was registered to DefaultChannelPipeline by making it part of the head context.

Result:

Less coupling and so be able to use DefaultChannelPipeline also with other Channel implementations that not extend AbstractChannel
2016-05-21 17:14:00 +02:00
..
src Decouple DefaultChannelPipeline from AbstractChannel 2016-05-21 17:14:00 +02:00
pom.xml [maven-release-plugin] prepare for next development iteration 2016-04-10 08:37:18 +02:00