Scott Mitchell 5b48fc284e Make OIO/NIO/EPOLL autoReadClear consistent ... Motivation: OIO/NIO use a volatile variable to track if a read is pending. EPOLL does not use a volatile an executes a Runnable on the event loop thread to set readPending to false. These mechansims should be consistent, and not using a volatile variable is preferable because the variable is written to frequently in the event loop thread. OIO also does not set readPending to false before each fireChannelRead operation and may result in reading more data than the user desires. Modifications: - OIO/NIO should not use a volatile variable for readPending - OIO should set readPending to false before each fireChannelRead Result: OIO/NIO/EPOLL are more consistent w.r.t. readPending and volatile variable operations are reduced Fixes https://github.com/netty/netty/issues/5069		2016-04-06 12:32:14 -07:00
..
bootstrap	Extract SocketAdress logic from NameResolver	2015-12-14 14:03:50 +01:00
channel	Make OIO/NIO/EPOLL autoReadClear consistent	2016-04-06 12:32:14 -07:00