Go to file
Norman Maurer 695fbc9140 [#2684] EpollSocketChannel gathering writes should take fast-path if possible
Motivation:

In EpollSocketchannel.writeBytesMultiple(...) we loop over all buffers to see if we need to adjust the readerIndex for incomplete writes. We can skip this if we know that everything was written (a.k.a complete write).

Modification:

Use fast-path if all bytes are written and so no need to loop over buffers

Result:

Fast write path for the average use.
2014-07-21 06:49:13 +02:00
all [maven-release-plugin] prepare for next development iteration 2014-07-04 17:26:02 +09:00
buffer Small performance improvements 2014-07-20 09:26:04 +02:00
codec Fixes for compression codecs 2014-07-20 09:32:53 +02:00
codec-dns Don't spin from malformed dns packets containing loops 2014-07-20 14:09:16 +02:00
codec-haproxy Fix NPE problems 2014-07-20 12:55:22 +02:00
codec-http Fix NPE problems 2014-07-20 12:55:22 +02:00
codec-memcache [maven-release-plugin] prepare for next development iteration 2014-07-04 17:26:02 +09:00
codec-mqtt Fix NPE problems 2014-07-20 12:55:22 +02:00
codec-socks [maven-release-plugin] prepare for next development iteration 2014-07-04 17:26:02 +09:00
codec-stomp Fix NPE problems 2014-07-20 12:55:22 +02:00
common Fix NPE problems 2014-07-20 12:55:22 +02:00
example Move generic code to HttpOrSpdyChooser to simplify implementations 2014-07-07 09:37:10 +02:00
handler Fix NPE problems 2014-07-20 12:55:22 +02:00
license Implemented a Bzip2Encoder 2014-07-17 16:19:39 +02:00
microbench [maven-release-plugin] prepare for next development iteration 2014-07-04 17:26:02 +09:00
tarball [maven-release-plugin] prepare for next development iteration 2014-07-04 17:26:02 +09:00
testsuite [#2647] Respect IOV_MAX when call writev in native transport 2014-07-09 12:21:58 +02:00
transport [#2680] NioSocketChannelOutboundBuffer.nioBuffers() / EpollSocketChannelOutboundBuffer.memoryAddresses() should always return non-null array as stated in javadocs 2014-07-20 19:57:01 +02:00
transport-native-epoll [#2684] EpollSocketChannel gathering writes should take fast-path if possible 2014-07-21 06:49:13 +02:00
transport-rxtx [maven-release-plugin] prepare for next development iteration 2014-07-04 17:26:02 +09:00
transport-sctp [maven-release-plugin] prepare for next development iteration 2014-07-04 17:26:02 +09:00
transport-udt [maven-release-plugin] prepare for next development iteration 2014-07-04 17:26:02 +09: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 Implemented a Bzip2Encoder 2014-07-17 16:19:39 +02:00
pom.xml Implemented LZF compression codec 2014-07-17 07:18:07 +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

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.