Go to file
Norman Maurer 9594a81b95 [#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:14:25 +02:00
all Add MQTT protocol codec 2014-06-21 16:52:10 +09:00
buffer [#2622] Correctly check reference count before try to work on the underlying memory 2014-06-30 07:14:25 +02:00
codec fix example missing break statement in ReplayingDecoder 2014-06-28 21:42:23 +02:00
codec-dns DNS codec for Netty which is based on the work of [#1622]. 2014-06-10 09:57:06 +02:00
codec-haproxy Fix test failures due to incorrect validation 2014-06-21 17:11:35 +09:00
codec-http Maintain decoder result in HttpObjectAggregator 2014-06-28 22:08:53 +02:00
codec-memcache Fix potential buffer leak in AbstractBinaryMemcacheDecoder 2014-06-24 16:25:40 +09:00
codec-mqtt Mqtt -> MQTT 2014-06-21 17:14:41 +09:00
codec-socks Deprecate SocksMessage.encodeAsByteBuf() 2014-06-24 16:40:44 +09:00
codec-stomp Introduce TextHeaders and AsciiString 2014-06-14 15:36:19 +09:00
common [#2604] Not try to use sun.misc.Cleaner when on android 2014-06-27 08:25:42 +02:00
example Remove 'get' prefix from all HTTP/SPDY messages 2014-06-24 18:03:33 +09:00
handler Refactor FastThreadLocal to simplify TLV management 2014-06-19 21:13:55 +09:00
license Implement a Bzip2Decoder 2014-06-24 14:50:09 +09:00
microbench Fix the inconsistencies between performance tests in ByteBufAllocatorBenchmark 2014-06-21 13:28:02 +09:00
tarball Update the version to 4.1.0.Alpha1-SNAPSHOT 2014-02-13 18:32:26 -08:00
testsuite Remove 'get' prefix from all HTTP/SPDY messages 2014-06-24 18:03:33 +09:00
transport Cleanup comment / code 2014-06-27 21:36:52 +02:00
transport-native-epoll Let EpollReuseAddrTest also work with kernel versions that not have bugfix release part 2014-06-27 17:56:17 +02:00
transport-rxtx Synchronized between 4.1 and master again (part 2) 2014-04-25 15:06:26 +09:00
transport-sctp Synchronized between 4.1 and master again (part 2) 2014-04-25 15:06:26 +09:00
transport-udt Synchronized between 4.1 and master again (part 2) 2014-04-25 15:06:26 +09: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: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 Implement a Bzip2Decoder 2014-06-24 14:50:09 +09:00
pom.xml Upgrade JACOCO to the latest version 2014-06-27 17:23:59 +09:00
README.md Synchronized between 4.1 and master 2014-04-25 00:38:02 +09: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.