844362a947
Motivation: While the default thread model provided by Netty is reasonable enough for most applications, some users might have a special requirement for the thread model. Here are a few examples: - A user might want to invoke handlers from the caller thread directly, assuming that his or her application is completely asynchronous and does not make any invocation from non-I/O thread. In this case, the default invoker implementation will only add the overhead of checking if the current thread is an I/O thread or not. - A user might want to invoke handlers from different threads depending on the type of events flexibly. Modifications: - Backport 132af3a485015ff912bd567a47881814d2ce1828 which is a fix for #1912 - Add a new interface called 'ChannelHandlerInvoker' that performs the invocation of event handler methods. - Add pipeline manipulation methods that accept ChannelHandlerInvoker - The differences from the original commit: - Separated the irrelevant changes out - Channel.eventLoop is null until the registration is complete in this branch, so Channel.Unsafe.invoker() doesn't work before registration. - Deregistration is not gone in this branch, so the methods related with deregistration were added to ChannelHandlerInvoker
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.
Branches to look
The 'master' branch is where the development of the latest major version lives on. The development of all other major versions takes place in each branch whose name is identical to its major version number. For example, the development of 3.x and 4.x resides in the branch '3' and the branch '4' respectively.