Go to file
Scott Mitchell 94ef424e1c Decouple Unix from Linux in Native Transport
Motivation:
transport-native-epoll is designed to be specific to Linux. However there is native code that can be extracted out and made to work on more Unix like distributions. There are a few steps to be completely decoupled but the first step is to extract out code that can run in a more general Unix environment from the Linux specific code base.

Modifications:
- Move all non-Linux specific stuff from Native.java into the io.netty.channel.unix package.
- io.netty.channel.unix.FileDescriptor will inherit all the native methods that are specific to file descriptors.
- io_netty_channel_epoll_Native.[c|h] will only have code that is specific to Linux.

Result:
Code is decoupled and design is streamlined in FileDescriptor.
2015-11-02 12:54:04 -08:00
all [maven-release-plugin] prepare for next development iteration 2015-09-30 09:31:26 +02:00
buffer Move isValid utility method to MathUtil 2015-10-30 15:38:16 -07:00
codec [#4284] Forward decoded messages more frequently 2015-10-07 14:15:14 +02:00
codec-haproxy [maven-release-plugin] prepare for next development iteration 2015-09-30 09:31:26 +02:00
codec-http Created RTSPEncoder and RTSPDecoder which are now common for both requests and responses to be able to handle both types of messages on the same channel. 2015-10-27 15:26:19 +01:00
codec-socks [maven-release-plugin] prepare for next development iteration 2015-09-30 09:31:26 +02:00
common Move isValid utility method to MathUtil 2015-10-30 15:38:16 -07:00
example [#4347] Remove not needed write operation from example. 2015-10-14 10:56:49 +02:00
handler [#4355] OpenSslServerContext reinitializes the provided TrustManagerFactory with the key cert chain. 2015-10-25 10:59:39 +01:00
license Let PoolThreadCache work even if allocation and deallocation Thread are different 2015-05-27 14:35:22 +02:00
microbench Fix performance regression in FastThreadLocal microbenchmark. Fixes #4402 2015-10-29 21:46:04 +01:00
tarball [maven-release-plugin] prepare for next development iteration 2015-09-30 09:31:26 +02:00
testsuite [maven-release-plugin] prepare for next development iteration 2015-09-30 09:31:26 +02:00
testsuite-osgi [maven-release-plugin] prepare for next development iteration 2015-09-30 09:31:26 +02:00
transport [#4363] Improve size calculation of messages when written from outside the EventLoop 2015-10-28 21:34:26 +01:00
transport-native-epoll Decouple Unix from Linux in Native Transport 2015-11-02 12:54:04 -08:00
transport-rxtx [maven-release-plugin] prepare for next development iteration 2015-09-30 09:31:26 +02:00
transport-sctp [#4327] Ensure toString() will not throw IllegalReferenceCountException 2015-10-10 20:12:19 +02:00
transport-udt [maven-release-plugin] prepare for next development iteration 2015-09-30 09:31:26 +02:00
.fbprefs
.gitignore Add JVM crash logs to .gitignore 2014-05-18 21:37:12 +09: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 Let PoolThreadCache work even if allocation and deallocation Thread are different 2015-05-27 14:35:22 +02:00
pom.xml Implement SSLSession.invalidate() and isValid() for OpenSSLEngine. 2015-10-15 12:02:04 +02:00
README.md Fix the 'branches to look' section 2015-10-27 13:58:06 +01:00
run-example.sh Add logLevel property to enable different log levels for the examples. 2014-11-21 10:48:13 +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 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.