Go to file
Trustin Lee 8cb6b779c9 Add io.netty.noJdkZlibEncoder system property
Related issue: #2821

Motivation:

There's no way for a user to change the default ZlibEncoder
implementation.

It is already possible to change the default ZlibDecoder implementation.

Modification:

Add a new system property 'io.netty.noJdkZlibEncoder'.

Result:

A user can disable JDK ZlibEncoder, just like he or she can disable JDK
ZlibDecoder.
2014-08-26 15:51:11 +09:00
all [maven-release-plugin] prepare for next development iteration 2014-08-16 03:27:42 +09:00
buffer [maven-release-plugin] prepare for next development iteration 2014-08-16 03:27:42 +09:00
codec Add io.netty.noJdkZlibEncoder system property 2014-08-26 15:51:11 +09:00
codec-dns [maven-release-plugin] prepare for next development iteration 2014-08-16 03:27:42 +09:00
codec-haproxy [maven-release-plugin] prepare for next development iteration 2014-08-16 03:27:42 +09:00
codec-http Reduce memory copies in spdy compression implementation. 2014-08-21 11:27:32 +02:00
codec-memcache [maven-release-plugin] prepare for next development iteration 2014-08-16 03:27:42 +09:00
codec-mqtt [maven-release-plugin] prepare for next development iteration 2014-08-16 03:27:42 +09:00
codec-socks codec-socks test cleanup 2014-08-20 06:53:37 +02:00
codec-stomp [maven-release-plugin] prepare for next development iteration 2014-08-16 03:27:42 +09:00
common Avoid redundant reads of head in peakNode 2014-08-21 09:01:22 +02:00
example Fix example for Http Upload 2014-08-18 10:48:54 +02:00
handler Support IPv4 default route in ipfilter. 2014-08-17 14:32:27 +02:00
license Implemented LZ4 compression codec 2014-08-14 15:05:24 -07:00
microbench [maven-release-plugin] prepare for next development iteration 2014-08-16 03:27:42 +09:00
tarball [maven-release-plugin] prepare for next development iteration 2014-08-16 03:27:42 +09:00
testsuite Better fix for TrafficShapingHandlerTest 2014-08-16 18:10:10 +02:00
transport [#2586] Use correct EventExecutor to notify for bind failures on late registration 2014-08-20 16:34:57 +02:00
transport-native-epoll Allow efficient writing of CompositeByteBuf when using native epoll transport. 2014-08-21 10:57:45 +02:00
transport-rxtx [maven-release-plugin] prepare for next development iteration 2014-08-16 03:27:42 +09:00
transport-sctp [maven-release-plugin] prepare for next development iteration 2014-08-16 03:27:42 +09:00
transport-udt [maven-release-plugin] prepare for next development iteration 2014-08-16 03:27:42 +09:00
.fbprefs Updated Find Bugs configuration 2009-03-04 10:33:09 +00:00
.gitignore Add JVM crash logs to .gitignore 2014-05-18 21:36:54 +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:13:58 +09:00
LICENSE.txt Relicensed to Apache License v2 2009-08-28 07:15:49 +00:00
NOTICE.txt Implemented LZ4 compression codec 2014-08-14 15:05:24 -07:00
pom.xml [maven-release-plugin] prepare for next development iteration 2014-08-16 03:27:42 +09:00
README.md Add a link to the 'native transports' page 2014-07-21 12:54:24 -07:00
run-example.sh Overall refactoring of the STOMP codec 2014-06-04 17:09:42 +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.