Go to file
Norman Maurer 02e7e53cbb [#2752] Add PendingWriteQueue for queue up writes
Motivation:

Sometimes ChannelHandler need to queue writes to some point and then process these. We currently have no datastructure for this so the user will use an Queue or something like this. The problem is with this Channel.isWritable() will not work as expected and so the user risk to write to fast. That's exactly what happened in our SslHandler. For this purpose we need to add a special datastructure which will also take care of update the Channel and so be sure that Channel.isWritable() works as expected.

Modifications:

- Add PendingWriteQueue which can be used for this purpose
- Make use of PendingWriteQueue in SslHandler

Result:

It is now possible to queue writes in a ChannelHandler and still have Channel.isWritable() working as expected. This also fixes #2752.
2014-08-12 06:38:22 +02:00
all [maven-release-plugin] prepare for next development iteration 2014-07-04 17:26:02 +09:00
buffer Port ChannelOutboundBuffer and related changes from 4.0 2014-08-05 15:00:45 +02:00
codec Consider writerIndex when LzfDecoder writes into a new heap buffer 2014-08-05 22:51:02 +02:00
codec-dns Fix buffer leaks in DnsResponseDecoder and DnsResponseDecoderTest 2014-08-04 14:06:45 +02:00
codec-haproxy Fix NPE problems 2014-07-20 12:55:22 +02:00
codec-http SPDY: fix SpdySessionHandler::updateSendWindowSize 2014-08-11 11:21:24 +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 a resource leak in StompSubframeAggregatorTest 2014-08-11 10:46:43 -07:00
common [#2744] Fix flakey HashedWheelTimerTest.testExecutionOnTime() 2014-08-06 07:03:31 +02:00
example Move generic code to HttpOrSpdyChooser to simplify implementations 2014-07-07 09:37:10 +02:00
handler [#2752] Add PendingWriteQueue for queue up writes 2014-08-12 06:38: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 [#2752] Add PendingWriteQueue for queue up writes 2014-08-12 06:38:22 +02:00
transport-native-epoll Port ChannelOutboundBuffer and related changes from 4.0 2014-08-05 15:00:45 +02:00
transport-rxtx [maven-release-plugin] prepare for next development iteration 2014-07-04 17:26:02 +09:00
transport-sctp Port ChannelOutboundBuffer and related changes from 4.0 2014-08-05 15:00:45 +02:00
transport-udt Port ChannelOutboundBuffer and related changes from 4.0 2014-08-05 15:00:45 +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: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 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.