andreacavalli/netty5
1
0
Fork 0
Code Issues Pull Requests Projects Releases Wiki Activity
5,928 Commits 27 Branches 234 Tags 84 MiB
Java 99.8%
Shell 0.1%
371f8066d2
Go to file
Norman Maurer 371f8066d2 [#2580] [#2587] Fix buffer corruption regression when ByteBuf.order(LITTLE_ENDIAN) is used 
Motivation:

To improve the speed of ByteBuf with order LITTLE_ENDIAN and where the native order is also LITTLE_ENDIAN (intel) we introduces a new special SwappedByteBuf before in commit 4ad3984c8b. Unfortunally the commit has a flaw which does not handle correctly the case when a ByteBuf expands. This was caused because the memoryAddress was cached and never changed again even if the underlying buffer expanded. This can lead to corrupt data or even to SEGFAULT the JVM if you are lucky enough.

Modification:

Always lookup the actual memoryAddress of the wrapped ByteBuf.

Result:

No more data-corruption for ByteBuf with order LITTLE_ENDIAN and no JVM crashes.
2014-06-20 18:24:44 +02:00
all Initial STOMP protocol work from @sskachkov 2014-06-04 17:09:42 +09:00
buffer [#2580] [#2587] Fix buffer corruption regression when ByteBuf.order(LITTLE_ENDIAN) is used 2014-06-20 18:24:44 +02:00
codec Refactor FastThreadLocal to simplify TLV management 2014-06-19 21:13:55 +09:00
codec-dns DNS codec for Netty which is based on the work of [#1622]. 2014-06-10 09:57:06 +02:00
codec-http Refactor FastThreadLocal to simplify TLV management 2014-06-19 21:13:55 +09:00
codec-memcache Introduce MessageAggregator and DecoderResultProvider 2014-06-05 16:51:14 +09:00
codec-socks Clean up the examples 2014-05-23 17:13:09 +09:00
codec-stomp Introduce TextHeaders and AsciiString 2014-06-14 15:36:19 +09:00
common Refactor FastThreadLocal to simplify TLV management 2014-06-19 21:13:55 +09:00
example Backport the additional AsciiString/TextHeader changes from master 2014-06-14 17:33:34 +09:00
handler Refactor FastThreadLocal to simplify TLV management 2014-06-19 21:13:55 +09:00
license Introduce TextHeaders and AsciiString 2014-06-14 15:36:19 +09:00
microbench Refactor FastThreadLocal to simplify TLV management 2014-06-19 21:13:55 +09:00
tarball Update the version to 4.1.0.Alpha1-SNAPSHOT 2014-02-13 18:32:26 -08:00
testsuite Introduce MessageAggregator and DecoderResultProvider 2014-06-05 16:51:14 +09:00
transport [#2586] Use correct EventLoop to notify delayed successful registration 2014-06-20 16:59:13 +02:00
transport-native-epoll Add an OpenSslEngine and the universal API for enabling SSL 2014-05-18 02:54:06 +09: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 Introduce TextHeaders and AsciiString 2014-06-14 15:36:19 +09:00
pom.xml export sun security packages as optional 2014-06-15 21:00:59 +02: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

README.md

Netty Project

Netty is an asynchronous event-driven network application framework for rapid development of maintainable high performance protocol servers & clients.

Links

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.