Go to file
Norman Maurer de76843905 Throw ReadOnlyBufferException if unsafe buffer is used and dst is direct
Motivation:

We missed to check if the dst is ready only before using unsafe to copy data into it which lead to data-corruption. We need to ensure we respect ready only ByteBuffer.

Modifications:

- Correctly check if the dst is ready only before copy data into it in UnsafeByteBufUtil
- Also make it work for buffers that are not direct and not have an array

Result:

No more data corruption possible if the dst buffer is readonly and unsafe buffer implementation is used.
2015-12-17 13:24:58 +01:00
all Fix version 2015-11-24 21:24:22 +01:00
buffer Throw ReadOnlyBufferException if unsafe buffer is used and dst is direct 2015-12-17 13:24:58 +01:00
codec Fix version 2015-11-24 21:24:22 +01:00
codec-haproxy Fix version 2015-11-24 21:24:22 +01:00
codec-http [#4505] Correctly handle whitespaces in websocket uri's. 2015-12-10 13:52:28 +01:00
codec-socks Fix version 2015-11-24 21:24:22 +01:00
common DefaultPromiseTest dead code removal 2015-12-11 10:34:24 -08:00
example Fix version 2015-11-24 21:24:22 +01:00
handler Throw exception if KeyManagerFactory is used with OpenSslServerContext 2015-12-17 08:01:36 +01:00
license Let PoolThreadCache work even if allocation and deallocation Thread are different 2015-05-27 14:35:22 +02:00
microbench Fix version 2015-11-24 21:24:22 +01:00
tarball Fix version 2015-11-24 21:24:22 +01:00
testsuite Fix version 2015-11-24 21:24:22 +01:00
testsuite-osgi Fix version 2015-11-24 21:24:22 +01:00
transport [#4449] Remove registered events from eventloop before close 2015-12-13 09:55:34 +01:00
transport-native-epoll [#4449] Remove registered events from eventloop before close 2015-12-13 09:55:34 +01:00
transport-rxtx Fix version 2015-11-24 21:24:22 +01:00
transport-sctp Fix version 2015-11-24 21:24:22 +01:00
transport-udt Fix version 2015-11-24 21:24:22 +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: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 Let PoolThreadCache work even if allocation and deallocation Thread are different 2015-05-27 14:35:22 +02:00
pom.xml Fix version 2015-11-24 21:24:22 +01:00
README.md Fix the 'branches to look' section 2015-10-27 13:58:06 +01:00
run-example.sh Add logLevel property to enable different log levels for the examples. 2014-11-21 10:48:13 +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.