Norman Maurer 0a8e1aaf19 Flush task should not flush messages that were written since last flush attempt. ... Motivation: The flush task is currently using flush() which will have the affect of have the flush traverse the whole ChannelPipeline and also flush messages that were written since we gave up flushing. This is not really correct as we should only continue to flush messages that were flushed at the point in time when the flush task was submitted for execution if the user not explicit call flush() by him/herself. Modification: Call *Unsafe.flush0() via the flush task which will only continue flushing messages that were marked as flushed before. Result: More correct behaviour when the flush task is used.		2018-03-02 10:09:40 +09:00
..
src	Flush task should not flush messages that were written since last flush attempt.	2018-03-02 10:09:40 +09:00
pom.xml	[maven-release-plugin] prepare for next development iteration	2018-02-21 12:52:33 +00:00