220660e351
Motivation: After a channel is created it's usually assigned to an EventLoop. During the lifetime of a Channel the EventLoop is then responsible for processing all I/O and compute tasks of the Channel. For various reasons (e.g. load balancing) a user might require the ability for a Channel to be assigned to another EventLoop during its lifetime. Modifications: Introduce under the hood changes that ensure that Netty's thread model is obeyed during and after the deregistration of a channel. Ensure that tasks (one time and periodic) are executed by the right EventLoop at all times. Result: A Channel can be deregistered from one and re-registered with another EventLoop.
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
The 'master' branch is where the development of the latest major version lives on. The development of all other 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.