andreacavalli/netty5
1
0
Fork 0
Code Issues Pull Requests Projects Releases Wiki Activity
5,821 Commits 27 Branches 234 Tags 84 MiB
Java 99.8%
Shell 0.1%
d8d822fddd
Go to file
Norman Maurer d8d822fddd Eliminate unnecessary extra synchronization in DefaultChannelPipeline 
Motivation:
At the moment whenever we add/remove a ChannelHandler with an EventExecutorGroup we have two synchronization points in the execution path. One to find the childInvoker and one for add/remove itself. We can eliminate the former by call findIInvoker in the synchronization block, as we need to synchronize anyway.

Modification:
Remove the usage of AtomicFieldUpdater and the extra synchronization in findInvoker by moving the call of the method in the synchronized(this) block.

Result:
Less synchronization points and volatile reads/writes
2014-04-25 14:15:23 +02:00
all Ensure native transport is included in all and tarball 2014-02-17 22:46:07 +01:00
buffer Synchronized between 4.1 and master 2014-04-25 00:38:02 +09:00
codec Synchronized between 4.1 and master 2014-04-25 00:38:02 +09:00
codec-http Synchronized between 4.1 and master (part 3) 2014-04-25 16:17:59 +09:00
codec-memcache Synchronized between 4.1 and master (part 3) 2014-04-25 16:17:59 +09:00
codec-socks Update the version to 4.1.0.Alpha1-SNAPSHOT 2014-02-13 18:32:26 -08:00
common Code clean-up 2014-04-25 17:44:04 +09:00
example Synchronized between 4.1 and master again (part 2) 2014-04-25 15:06:26 +09:00
handler Undeprecate deregister() and chanelUnregistered() 2014-04-25 16:40:42 +09:00
license [#1259] Add optimized queue for SCMP pattern and use it in NIO and native transport 2014-02-27 13:28:37 +01:00
microbench Upgrade JMH to 0.4.1 and make use of @Params. 2014-02-23 16:39:39 +01:00
tarball Update the version to 4.1.0.Alpha1-SNAPSHOT 2014-02-13 18:32:26 -08:00
testsuite Synchronized between 4.1 and master 2014-04-25 00:38:02 +09:00
transport Eliminate unnecessary extra synchronization in DefaultChannelPipeline 2014-04-25 14:15:23 +02:00
transport-native-epoll Synchronized between 4.1 and master again (part 2) 2014-04-25 15:06:26 +09:00
transport-rxtx Synchronized between 4.1 and master again (part 2) 2014-04-25 15:06:26 +09:00
transport-sctp Synchronized between 4.1 and master again (part 2) 2014-04-25 15:06:26 +09:00
transport-udt Synchronized between 4.1 and master again (part 2) 2014-04-25 15:06:26 +09:00
.fbfilter.xml Update license headers 2012-06-04 13:31:44 -07:00
.fbprefs Updated Find Bugs configuration 2009-03-04 10:33:09 +00:00
.gitignore Format and partially describe Gitignore 2013-12-10 07:04:38 +01: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 [#1259] Add optimized queue for SCMP pattern and use it in NIO and native transport 2014-02-27 13:28:37 +01:00
pom.xml Mark sun.nio.ch as optional 2014-04-23 10:37:14 +02:00
README.md Synchronized between 4.1 and master 2014-04-25 00:38:02 +09:00

README.md

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:

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.