Go to file
Norman Maurer 02c3e71012 [#2376] Add support for SO_REUSEPORT in native transport
Motivation:
In linux kernel 3.9 a new featured named SO_REUSEPORT was introduced which allows to have multiple sockets bind to the same port and so handle the accept() of new connections with multiple threads. This can greatly improve the performance when you not to accept a lot of connections.

Modifications:
Implement SO_REUSEPORT via JNI

Result:
Be able to use the SO_REUSEPORT feature when using the EpollServerSocketChannel
2014-04-16 14:25:02 +02:00
all [maven-release-plugin] prepare for next development iteration 2014-04-01 07:21:40 +02:00
buffer Fix error that causes (up to) double memory usage 2014-04-15 07:02:49 +02:00
codec [#2353] Use a privileged block to get ClassLoader and System property if needed 2014-04-08 13:59:03 +02:00
codec-http Fix missed buffer leaks in SpdyFrameDecoderTest 2014-04-16 14:03:12 +02:00
codec-socks [maven-release-plugin] prepare for next development iteration 2014-04-01 07:21:40 +02:00
common [#2353] Use a privileged block to get ClassLoader and System property if needed 2014-04-08 13:59:03 +02:00
example SPDY: refactor frame codec implementation 2014-04-15 20:05:05 +02:00
handler [#2353] Use a privileged block to get ClassLoader and System property if needed 2014-04-08 13:59:03 +02:00
license [#1259] Add optimized queue for SCMP pattern and use it in NIO and native transport 2014-02-27 11:44:06 +01:00
microbench [maven-release-plugin] prepare for next development iteration 2014-04-01 07:21:40 +02:00
tarball [maven-release-plugin] prepare for next development iteration 2014-04-01 07:21:40 +02:00
testsuite SPDY: refactor frame codec implementation 2014-04-15 20:05:05 +02:00
transport [#2390] Minimize memory usage of NioDatagramChannel 2014-04-15 06:55:51 +02:00
transport-native-epoll [#2376] Add support for SO_REUSEPORT in native transport 2014-04-16 14:25:02 +02:00
transport-rxtx [maven-release-plugin] prepare for next development iteration 2014-04-01 07:21:40 +02:00
transport-sctp [maven-release-plugin] prepare for next development iteration 2014-04-01 07:21:40 +02:00
transport-udt [maven-release-plugin] prepare for next development iteration 2014-04-01 07:21:40 +02: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:18:14 +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 11:44:06 +01:00
pom.xml [maven-release-plugin] prepare for next development iteration 2014-04-01 07:21:40 +02:00
README.md Update README.md 2014-01-16 14:38:36 +09: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

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.