Go to file
Norman Maurer 6c47cc9711 [#2622] Correctly check reference count before try to work on the underlying memory
Motivation:

Because of how we use reference counting we need to check for the reference count before each operation that touches the underlying memory. This is especially true as we use sun.misc.Cleaner.clean() to release the memory ASAP when possible. Because of this the user may cause a SEGFAULT if an operation is called that tries to access the backing memory after it was released.

Modification:

Correctly check the reference count on all methods that access the underlying memory or expose it via a ByteBuffer.

Result:

Safer usage of ByteBuf
2014-06-30 07:10:12 +02:00
all [maven-release-plugin] prepare for next development iteration 2014-06-12 16:20:52 +02:00
buffer [#2622] Correctly check reference count before try to work on the underlying memory 2014-06-30 07:10:12 +02:00
codec fix example missing break statement in ReplayingDecoder 2014-06-28 21:42:46 +02:00
codec-http Maintain decoder result in HttpObjectAggregator 2014-06-28 21:47:49 +02:00
codec-socks Deprecate SocksMessage.encodeAsByteBuf() 2014-06-24 16:41:47 +09:00
common [#2604] Not try to use sun.misc.Cleaner when on android 2014-06-27 08:18:21 +02:00
example Partially revert 4a13f66e13 2014-06-27 16:40:43 +09:00
handler Refactor FastThreadLocal to simplify TLV management 2014-06-19 21:08:16 +09:00
license Preparation for porting OpenSSL support in 3.10 2014-05-17 20:01:47 +09:00
microbench Fix the inconsistencies between performance tests in ByteBufAllocatorBenchmark 2014-06-21 13:28:11 +09:00
tarball [maven-release-plugin] prepare for next development iteration 2014-06-12 16:20:52 +02:00
testsuite Partially revert 4a13f66e13 2014-06-27 16:40:43 +09:00
transport Cleanup comment / code 2014-06-27 21:35:54 +02:00
transport-native-epoll Let EpollReuseAddrTest also work with kernel versions that not have bugfix release part 2014-06-27 17:56:31 +02:00
transport-rxtx [maven-release-plugin] prepare for next development iteration 2014-06-12 16:20:52 +02:00
transport-sctp [maven-release-plugin] prepare for next development iteration 2014-06-12 16:20:52 +02:00
transport-udt [maven-release-plugin] prepare for next development iteration 2014-06-12 16:20:52 +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 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 Preparation for porting OpenSSL support in 3.10 2014-05-17 20:01:47 +09:00
pom.xml Upgrade JACOCO to the latest version 2014-06-27 17:23:03 +09:00
README.md Update README.md 2014-01-16 14:38:36 +09:00
run-example.sh Use a forked exec-maven-plugin instead of maven-antrun-plugin 2014-05-23 20:06:12 +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.