Go to file
Norman Maurer 98925a1fa4 Move generic unix classes/interfaces out of epoll package
Motivation:

As we plan to have other native transports soon (like a kqueue transport) we should move unix classes/interfaces out of the epoll package so we
introduce other implementations without breaking stuff before the next stable release.

Modifications:

Create a new io.netty.channel.unix package and move stuff over there.

Result:

Possible to introduce other native impls beside epoll.
2015-02-17 18:41:18 +01:00
all Fix missing version properties of transport-epoll in all-in-one JAR 2014-10-21 22:36:19 +09:00
buffer Ensure CompositeByteBuf.addComponent* handles buffer in consistent way and not causes leaks 2015-02-12 16:09:54 +01:00
codec Avoid unnecessary call to ByteBuf.isReadable() from ByteToMessageDecoder 2015-02-16 07:37:28 +01:00
codec-dns Add EDNS support to DnsQueryEncoder 2014-10-16 17:06:20 +09:00
codec-haproxy Fix NPE problems 2014-07-20 12:55:08 +02:00
codec-http Fix compile error introduced by 6e942a3a20 2015-02-06 12:54:12 +01:00
codec-http2 Removing debugging change from unit test. 2015-02-11 09:06:36 -08:00
codec-memcache Add proxy support for client socket connections 2014-10-14 12:40:33 +09:00
codec-mqtt Fix dependency issues with hamcrest 2014-12-04 17:53:35 +09:00
codec-socks Remove io.netty.handler.codec.socks 2015-02-10 11:38:21 +09:00
codec-stomp Headers set/add/contains timeMillis methods 2014-12-06 22:40:45 +09:00
common Revamp io.netty.handler.codec.socksx 2015-02-10 09:16:29 +09:00
example Revamp io.netty.handler.codec.socksx 2015-02-10 09:16:29 +09:00
handler Various performance optimizations in OpenSslEngine 2015-02-09 06:20:30 +01:00
handler-proxy Revamp io.netty.handler.codec.socksx 2015-02-10 09:16:29 +09:00
license Implemented LZMA frame encoder 2014-09-15 15:14:15 +02:00
microbench Fix ByteBufUtilBenchmark on utf8 encodings. 2014-12-31 20:26:50 +09:00
osgitests Add a pax-exam based OSGi test suite 2015-02-16 15:56:58 +01:00
resolver Fix memory leak in NameResolverGroup 2014-11-20 20:22:17 +09:00
resolver-dns Remove thepiratebay.se from the test domain list 2014-12-22 22:35:58 +09:00
tarball [maven-release-plugin] prepare for next development iteration 2013-12-22 22:06:15 +09:00
testsuite Allow to use WebSocketClientHandshaker and WebSocketServerHandshaker with HttpResponse / HttpRequest 2015-02-06 10:47:08 +01:00
transport Move generic unix classes/interfaces out of epoll package 2015-02-17 18:41:18 +01:00
transport-native-epoll Move generic unix classes/interfaces out of epoll package 2015-02-17 18:41:18 +01:00
transport-rxtx Fix most inspector warnings 2014-07-02 19:04:11 +09:00
transport-sctp Allow to obtain RecvByteBufAllocator.Handle to allow more flexible implementations 2014-08-12 06:54:29 +02:00
transport-udt Fix typo in param name 2015-01-16 20:32:57 +01:00
.fbprefs Updated Find Bugs configuration 2009-03-04 10:33:09 +00:00
.gitignore Exclude bin directory from git Motivation: 2014-08-27 06:33:22 +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:17:58 +09:00
LICENSE.txt Relicensed to Apache License v2 2009-08-28 07:15:49 +00:00
NOTICE.txt Implemented LZMA frame encoder 2014-09-15 15:14:15 +02:00
pom.xml Add a pax-exam based OSGi test suite 2015-02-16 15:56:58 +01:00
README.md Add a link to the 'native transports' page 2014-07-21 12:10:16 -07:00
run-example.sh Add logLevel property to enable different log levels for the examples. 2014-11-21 10:49:27 +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.