Go to file
Xiaoyan Lin 751ed6cc94 Avoid unnecessary boxing/unboxing
Motivation:

Boxing/unboxing can be avoided.

Modifications:

Use parseInt/parseLong to avoid unnecessary boxing/unboxing.

Result:

Remove unnecessary boxing/unboxing.
2016-01-08 17:38:20 +01:00
all [maven-release-plugin] prepare for next development iteration 2015-11-10 22:59:33 +01:00
buffer Unpooled and Wrapped Buffer Leak 2016-01-07 12:02:52 -08:00
codec [#4635] Stop decoding if decoder was removed 2016-01-05 11:01:24 +01:00
codec-dns [maven-release-plugin] prepare for next development iteration 2015-11-10 22:59:33 +01:00
codec-haproxy [maven-release-plugin] prepare for next development iteration 2015-11-10 22:59:33 +01:00
codec-http Avoid unnecessary boxing/unboxing 2016-01-08 17:38:20 +01:00
codec-http2 Revert "Fix unnecessary boxing and incorrect Serializable" 2015-12-31 14:48:10 +01:00
codec-memcache [maven-release-plugin] prepare for next development iteration 2015-11-10 22:59:33 +01:00
codec-mqtt [maven-release-plugin] prepare for next development iteration 2015-11-10 22:59:33 +01:00
codec-socks [maven-release-plugin] prepare for next development iteration 2015-11-10 22:59:33 +01:00
codec-stomp [maven-release-plugin] prepare for next development iteration 2015-11-10 22:59:33 +01:00
codec-xml [maven-release-plugin] prepare for next development iteration 2015-11-10 22:59:33 +01:00
common Introduce DnsCache API + DnsResolver extensibility 2016-01-08 14:46:47 +01:00
example Avoid unnecessary boxing/unboxing 2016-01-08 17:38:20 +01:00
handler Unpooled and Wrapped Buffer Leak 2016-01-07 12:02:52 -08:00
handler-proxy Extract SocketAdress logic from NameResolver 2015-12-14 14:03:50 +01:00
license [#4331] Helper methods to get charset from Content-Type header of HttpMessage 2015-11-19 15:59:34 -08:00
microbench Fix errors reported by javadoc 2015-12-27 08:36:45 +01:00
resolver Fix errors reported by javadoc 2015-12-27 08:36:45 +01:00
resolver-dns Introduce DnsCache API + DnsResolver extensibility 2016-01-08 14:46:47 +01:00
tarball [maven-release-plugin] prepare for next development iteration 2015-11-10 22:59:33 +01:00
testsuite Removed unused imports 2016-01-04 14:32:29 +01:00
testsuite-osgi [maven-release-plugin] prepare for next development iteration 2015-11-10 22:59:33 +01:00
transport Avoid unnecessary boxing/unboxing 2016-01-08 17:38:20 +01:00
transport-native-epoll [#4658] Fix encoding of pom.xml file 2016-01-06 08:11:37 +01:00
transport-rxtx Fix errors reported by javadoc 2015-12-27 08:36:45 +01:00
transport-sctp Improve SctpMessage.hashCode method 2016-01-05 20:30:52 +01:00
transport-udt [maven-release-plugin] prepare for next development iteration 2015-11-10 22:59:33 +01: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 [#4331] Helper methods to get charset from Content-Type header of HttpMessage 2015-11-19 15:59:34 -08:00
pom.xml Fix deprecated Maven expressions usage 2016-01-08 14:38:33 +01:00
README.md Fix the 'branches to look' section 2015-10-27 13:59:11 +01:00
run-example.sh Add HTTP/2 Netty tiles example 2015-05-18 14:16:54 -07: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.