Roger Kapsi 68a941c091 Detecting actual Channel write idleness vs. slowness ... Motivation The IdleStateHandler tracks write() idleness on message granularity but does not take into consideration that the client may be just slow and has managed to consume a subset of the message's bytes in the configured period of time. Modifications Adding an optional configuration parameter to IdleStateHandler which tells it to observe ChannelOutboundBuffer's state. Result Fixes https://github.com/netty/netty/issues/6150		2016-12-30 17:22:07 -08:00
..
src	Detecting actual Channel write idleness vs. slowness	2016-12-30 17:22:07 -08:00
pom.xml	[maven-release-plugin] prepare for next development iteration	2016-10-14 13:20:41 +02:00