Go to file
Trustin Lee 9ee51fc4c7 Fix the regression caused by f31c630c8c
f31c630c8c was causing
SocketGatheringWriteTest to fail because it does not take the case where
an empty buffer exists in a gathering write.

When there is an empty buffer in a gathering write, the number of
buffers returned by ChannelOutboundBuffer.nioBuffer() and the actual
number of write attemps can differ.

To remove the write requests correctly, a byte transport must use
ChannelOutboundBuffer.removeBytes()
2014-08-15 09:43:56 -07:00
all [maven-release-plugin] prepare for next development iteration 2014-08-15 09:31:03 +09:00
buffer [maven-release-plugin] prepare for next development iteration 2014-08-15 09:31:03 +09:00
codec [maven-release-plugin] prepare for next development iteration 2014-08-15 09:31:03 +09:00
codec-dns [maven-release-plugin] prepare for next development iteration 2014-08-15 09:31:03 +09:00
codec-haproxy [maven-release-plugin] prepare for next development iteration 2014-08-15 09:31:03 +09:00
codec-http [maven-release-plugin] prepare for next development iteration 2014-08-15 09:31:03 +09:00
codec-memcache [maven-release-plugin] prepare for next development iteration 2014-08-15 09:31:03 +09:00
codec-mqtt [maven-release-plugin] prepare for next development iteration 2014-08-15 09:31:03 +09:00
codec-socks [maven-release-plugin] prepare for next development iteration 2014-08-15 09:31:03 +09:00
codec-stomp [maven-release-plugin] prepare for next development iteration 2014-08-15 09:31:03 +09:00
common [maven-release-plugin] prepare for next development iteration 2014-08-15 09:31:03 +09:00
example [maven-release-plugin] prepare for next development iteration 2014-08-15 09:31:03 +09:00
handler [maven-release-plugin] prepare for next development iteration 2014-08-15 09:31:03 +09:00
license Implemented LZ4 compression codec 2014-08-14 15:05:24 -07:00
microbench [maven-release-plugin] prepare for next development iteration 2014-08-15 09:31:03 +09:00
tarball [maven-release-plugin] prepare for next development iteration 2014-08-15 09:31:03 +09:00
testsuite [#2769] Fix regression when writing different message types 2014-08-15 11:56:12 +02:00
transport Fix the regression caused by f31c630c8c 2014-08-15 09:43:56 -07:00
transport-native-epoll [maven-release-plugin] prepare for next development iteration 2014-08-15 09:31:03 +09:00
transport-rxtx [maven-release-plugin] prepare for next development iteration 2014-08-15 09:31:03 +09:00
transport-sctp [maven-release-plugin] prepare for next development iteration 2014-08-15 09:31:03 +09:00
transport-udt [maven-release-plugin] prepare for next development iteration 2014-08-15 09:31:03 +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 LZ4 compression codec 2014-08-14 15:05:24 -07:00
pom.xml [maven-release-plugin] prepare for next development iteration 2014-08-15 09:31:03 +09:00
README.md Add a link to the 'native transports' page 2014-07-21 12:54:24 -07: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.