Go to file
Roger Kapsi 02850da480 Rename ChannelHandlerContext#fireUserEventTriggered() argument from event to evt so it matches the ChannelInboundHandler#userEventTriggered() argument's name.
Motivation

When I override ChannelHandler methods I usually (always) refire events myself via
ChannelHandlerContext instead of relieing on calling the super method (say
`super.write(ctx, ...)`). This works great and the IDE actually auto completes/generates
the right code for it except `#fireUserEventTriggered()` and `#userEventTriggered()`
which have a mismatching argument names and I have to manually "intervene".

Modification

Rename `ChannelHandlerContext#fireUserEventTriggered()` argument from `event` to `evt`
to match its handler counterpart.

Result

The IDE's auto generated code will reference the correct variable.
2016-07-07 17:01:19 +02:00
all [maven-release-plugin] prepare for next development iteration 2016-07-01 10:33:32 +02:00
buffer [maven-release-plugin] prepare for next development iteration 2016-07-01 10:33:32 +02:00
codec [maven-release-plugin] prepare for next development iteration 2016-07-01 10:33:32 +02:00
codec-dns [maven-release-plugin] prepare for next development iteration 2016-07-01 10:33:32 +02:00
codec-haproxy [maven-release-plugin] prepare for next development iteration 2016-07-01 10:33:32 +02:00
codec-http Fix set100ContinueExpected(...) jsvadoc 2016-07-04 19:03:14 +02:00
codec-http2 Revert "DefaultPromise make listeners not volatile" 2016-07-07 08:37:41 +02:00
codec-memcache [maven-release-plugin] prepare for next development iteration 2016-07-01 10:33:32 +02:00
codec-mqtt [maven-release-plugin] prepare for next development iteration 2016-07-01 10:33:32 +02:00
codec-redis [maven-release-plugin] prepare for next development iteration 2016-07-01 10:33:32 +02:00
codec-smtp [maven-release-plugin] prepare for next development iteration 2016-07-01 10:33:32 +02:00
codec-socks [maven-release-plugin] prepare for next development iteration 2016-07-01 10:33:32 +02:00
codec-stomp [maven-release-plugin] prepare for next development iteration 2016-07-01 10:33:32 +02:00
codec-xml [maven-release-plugin] prepare for next development iteration 2016-07-01 10:33:32 +02:00
common [#5486] Not operate on serial execution assumption when using EventExecutor in the DefaultChannelPipeline. 2016-07-07 15:01:56 +02:00
example [maven-release-plugin] prepare for next development iteration 2016-07-01 10:33:32 +02:00
handler Add FlushConsolidationHandler which consolidates flush operations as these are expensive 2016-07-07 06:48:23 +02:00
handler-proxy [maven-release-plugin] prepare for next development iteration 2016-07-01 10:33:32 +02:00
license added support for Protobuf codec nano runtime 2016-01-19 21:39:17 +01:00
microbench [maven-release-plugin] prepare for next development iteration 2016-07-01 10:33:32 +02:00
resolver [maven-release-plugin] prepare for next development iteration 2016-07-01 10:33:32 +02:00
resolver-dns [maven-release-plugin] prepare for next development iteration 2016-07-01 10:33:32 +02:00
tarball [maven-release-plugin] prepare for next development iteration 2016-07-01 10:33:32 +02:00
testsuite [maven-release-plugin] prepare for next development iteration 2016-07-01 10:33:32 +02:00
testsuite-osgi [maven-release-plugin] prepare for next development iteration 2016-07-01 10:33:32 +02:00
transport Rename ChannelHandlerContext#fireUserEventTriggered() argument from event to evt so it matches the ChannelInboundHandler#userEventTriggered() argument's name. 2016-07-07 17:01:19 +02:00
transport-native-epoll EPOLL Cached ECONNREFUSED Exception 2016-07-06 12:02:42 -07:00
transport-rxtx [maven-release-plugin] prepare for next development iteration 2016-07-01 10:33:32 +02:00
transport-sctp [maven-release-plugin] prepare for next development iteration 2016-07-01 10:33:32 +02:00
transport-udt [maven-release-plugin] prepare for next development iteration 2016-07-01 10:33:32 +02:00
.fbprefs Updated Find Bugs configuration 2009-03-04 10:33:09 +00:00
.gitignore Use shaded dependency on JCTools instead of copy and paste 2016-06-10 13:19:45 +02:00
.travis.yml Travis CI branch whitelisting 2013-03-11 09:55:43 +09:00
CONTRIBUTING.md Move the pull request guide to the developer guide 2014-03-12 13:13:58 +09:00
LICENSE.txt Relicensed to Apache License v2 2009-08-28 07:15:49 +00:00
NOTICE.txt added support for Protobuf codec nano runtime 2016-01-19 21:39:17 +01:00
pom.xml [maven-release-plugin] prepare for next development iteration 2016-07-01 10:33:32 +02:00
README.md Updating Branches to look section to match the current branching structure of the project 2016-03-10 22:08:01 +01:00
run-example.sh Add an example client for codec-redis 2016-04-23 11:18:12 -07:00

Netty Project

Netty is an asynchronous event-driven network application framework for rapid development of maintainable high performance protocol servers & clients.

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:

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.