3cfcf09af8
The problem with the old way was that we always set the OP_WRITE when the buffer could not be written until the write-spin-count was reached. This means that in some cases the channel was still be writable but we just was not able to write out the data quick enough. For this cases we should better break out the write loop and schedule a write to be picked up later in the EventLoop, when other tasks was executed. The OP_WRITE will only be set if a write actual returned 0 which means there is no more room for writing data and this we need to wait for the os to notify us.
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
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.