Go to file
Norman Maurer c46b197c61 [#2761] Proper work-around for data-corruption caused by cached ByteBuffers
Motivation:

The previous fix did disable the caching of ByteBuffers completely which can cause performance regressions. This fix makes sure we use nioBuffers() for all writes in NioSocketChannel and so prevent data-corruptions. This is still kind of a workaround which will be replaced by a more fundamental fix later.

Modifications:

- Revert 4059c9f354
- Use nioBuffers() for all writes to prevent data-corruption

Result:

No more data-corruption but still retain the original speed.
2014-08-13 21:21:15 +02:00
all [maven-release-plugin] prepare for next development iteration 2014-06-30 14:31:08 +02:00
buffer Refactoring in preparation to unify I/O logic for all branches 2014-08-05 08:04:23 +02:00
codec [#2705] Call fireChannelReadComplete() if channelActive(...) decodes messages in ReplayingDecoder / ByteToMessageDecoder 2014-07-24 14:33:56 +02:00
codec-http SPDY: fix SpdySessionHandler::updateSendWindowSize 2014-08-11 11:27:58 +02:00
codec-socks Fix most inspector warnings 2014-07-02 20:21:30 +09:00
common [#2744] Fix flakey HashedWheelTimerTest.testExecutionOnTime() 2014-08-06 07:03:58 +02:00
example Move generic code to HttpOrSpdyChooser to simplify implementations 2014-07-07 09:34:33 +02:00
handler [#2722] Improve Traffic Shaping Handling 2014-08-13 01:29:58 +02:00
license Remove license of deque as we not use it anymore 2014-08-04 12:21:33 +02:00
microbench [maven-release-plugin] prepare for next development iteration 2014-06-30 14:31:08 +02:00
tarball [maven-release-plugin] prepare for next development iteration 2014-06-30 14:31:08 +02:00
testsuite [#2722] Improve Traffic Shaping Handling 2014-08-13 01:29:58 +02:00
transport [#2761] Proper work-around for data-corruption caused by cached ByteBuffers 2014-08-13 21:21:15 +02:00
transport-native-epoll Refactoring in preparation to unify I/O logic for all branches 2014-08-05 08:04:23 +02:00
transport-rxtx Fix most inspector warnings 2014-07-02 20:21:30 +09:00
transport-sctp Refactoring in preparation to unify I/O logic for all branches 2014-08-05 08:04:23 +02:00
transport-udt Refactoring in preparation to unify I/O logic for all branches 2014-08-05 08:04:23 +02: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 Remove license of deque as we not use it anymore 2014-08-04 12:21:33 +02:00
pom.xml Add missing m2eclipse life cycle mapping 2014-07-06 16:53:53 +09:00
README.md Add a link to the 'native transports' page 2014-07-21 12:54:43 -07: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.