4950a523a7
Motivation: We need to break out of the read loop for two reasons: - If the input was shutdown in between (which may be the case when the user did it in the fireChannelRead(...) method we should not try to read again to not produce any miss-leading exceptions. - If the user closes the channel we need to ensure we not try to read from it again as the filedescriptor may be re-used already by the OS if the system is handling a lot of concurrent connections and so needs a lot of filedescriptors. If not do this we risk reading data from a filedescriptor that belongs to another socket then the socket that was "wrapped" by this Channel implementation. Modification: Break the reading loop if the input was shutdown from within the channelRead(...) method. Result: No more meaningless exceptions and no risk to read data from wrong socket after the original was closed.
Netty Project
Netty is an asynchronous event-driven network application framework for rapid development of maintainable high performance protocol servers & clients.
Links
How to build
For the detailed information about building and developing Netty, please visit the developer guide. This page only gives very basic information.
You require the following to build Netty:
- Latest stable Oracle JDK 7
- Latest stable Apache Maven
- If you are on Linux, you need additional development packages installed on your system, because you'll build the native transport.
Note that this is build-time requirement. JDK 5 (for 3.x) or 6 (for 4.0+) is enough to run your Netty-based application.
Branches to look
Development of all versions takes place in each branch whose name is identical to <majorVersion>.<minorVersion>. For example, the development of 3.9 and 4.0 resides in the branch '3.9' and the branch '4.0' respectively.