netty5/transport
Norman Maurer 0615e538c1 Not trigger channelWritabilityChanged if fail messages before close Channel.
Motivation:

We should not trigger channelWritabilityChanged during failing message when we are about to close the Channel as otherwise the use may try again writing even if the Channel is about to get closed.

Modifications:

Add new boolean param to ChannelOutboundBuffer.failFlushed(...) which allows to specify if we should notify or not.

Result:

channelWritabilityChanged is not triggered anymore if we cloe the Channel because of an IOException during write.
2015-05-06 21:38:39 +02:00
..
src Not trigger channelWritabilityChanged if fail messages before close Channel. 2015-05-06 21:38:39 +02:00
pom.xml [maven-release-plugin] prepare for next development iteration 2015-03-03 08:30:59 -05:00