Go to file
Norman Maurer a74149e984 [#1865] Only use internalNioBuffer when one of the read* or write* methods are used. This is neccessary to prevent races as those can happen when a slice or duplicate is shared between different Channels
that are not assigned to the same EventLoop. In general get* operations should always be safe to be used from different Threads.

This aslo include unit tests that show the issue
2013-09-25 17:27:26 +02:00
all Bump up version to reflect correct one 2013-09-09 11:20:12 +02:00
buffer [#1865] Only use internalNioBuffer when one of the read* or write* methods are used. This is neccessary to prevent races as those can happen when a slice or duplicate is shared between different Channels 2013-09-25 17:27:26 +02:00
codec Bump up version to reflect correct one 2013-09-09 11:20:12 +02:00
codec-http HttpRequestEncoder should append '/' to absolute path requests only when needed 2013-09-22 13:41:35 +02:00
codec-socks Bump up version to reflect correct one 2013-09-09 11:20:12 +02:00
common Bump up version to reflect correct one 2013-09-09 11:20:12 +02:00
example No need to use an unreleasable buffer - just wrap an array 2013-09-14 11:59:51 +02:00
handler Propagate channelWritabilityChanged() through the pipeline after flushing. Related to [#1861] 2013-09-24 14:05:25 +02:00
license Add back jzlib license file and notice 2013-02-21 14:00:59 -08:00
microbench Bump up version to reflect correct one 2013-09-09 11:20:12 +02:00
tarball Bump up version to reflect correct one 2013-09-09 11:20:12 +02:00
testsuite Introduce a new ChannelOption called DATAGRAM_CHANNEL_ACTIVE_ON_REGISTRATION. Related to [#1830] 2013-09-24 11:46:49 +02:00
testsuite-osgi Bump up version to reflect correct one 2013-09-09 11:20:12 +02:00
transport Introduce a new ChannelOption called DATAGRAM_CHANNEL_ACTIVE_ON_REGISTRATION. Related to [#1830] 2013-09-24 11:46:49 +02:00
transport-rxtx Bump up version to reflect correct one 2013-09-09 11:20:12 +02:00
transport-sctp Bump up version to reflect correct one 2013-09-09 11:20:12 +02:00
transport-udt Bump up version to reflect correct one 2013-09-09 11:20:12 +02: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 Allow per-write promises and disallow promises on flush() 2013-07-11 00:49:48 +09:00
.travis.yml Travis CI branch whitelisting 2013-03-11 09:55:43 +09:00
LICENSE.txt Relicensed to Apache License v2 2009-08-28 07:15:49 +00:00
NOTICE.txt Add back jzlib license file and notice 2013-02-21 14:00:59 -08:00
pom.xml Set memory for compiler as otherwise it sometimes fails here 2013-09-10 18:38:15 +02:00
README.md Fix broken url 2013-02-26 16:29:24 -08: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