andreacavalli/netty5
1
0
Fork 0
Code Issues Pull Requests Projects Releases Wiki Activity
6,059 Commits 27 Branches 234 Tags 84 MiB
Java 99.8%
Shell 0.1%
2fadef31ef
Go to file
Trustin Lee 2fadef31ef Fire channelRead() event immediately in OIO message channels 
Related: #3189

Motivation:

OIO transport implementations block for at most 1 second to wait for
additional messages (or accepted connections).

However, because AbstractOioMessageChannel defers the channelRead()
events for the messages read so far until there's nothing to read up to
maxMessagesPerRead, any read operation will be followed by a 1-second
delay.

Modifications:

Fire channelRead() events as soon as doRead() returns so that there is
no 1 second delay between the actual read and the channelRead() event.

Result:

No more weird 1-second delay
2014-12-07 12:13:33 +09:00
all [maven-release-plugin] prepare for next development iteration 2014-10-29 11:48:40 +01:00
buffer Small performance improvements 2014-11-20 00:58:35 -05:00
codec Rocumented decoder pitfalls to avoid mistakes found in [#3184] 2014-12-01 20:26:09 +01:00
codec-http Small performance improvements 2014-11-20 00:58:35 -05:00
codec-socks [maven-release-plugin] prepare for next development iteration 2014-10-29 11:48:40 +01:00
common Fix a bug where Recycler's capacity can increase beyond its maximum 2014-12-06 17:56:10 +09:00
example Do not write LastHttpContent twice in HttpStaticFileServer example 2014-11-21 11:46:10 +09:00
handler Overall clean-up of the initial SniHandler/DomainNameMapping work 2014-12-04 18:23:24 +09:00
license Remove license of deque as we not use it anymore 2014-08-04 12:21:33 +02:00
microbench Benchmark for HttpRequestDecoder 2014-11-12 14:37:11 +01:00
tarball [maven-release-plugin] prepare for next development iteration 2014-10-29 11:48:40 +01:00
testsuite [maven-release-plugin] prepare for next development iteration 2014-10-29 11:48:40 +01:00
transport Fire channelRead() event immediately in OIO message channels 2014-12-07 12:13:33 +09:00
transport-native-epoll [maven-release-plugin] prepare for next development iteration 2014-10-29 11:48:40 +01:00
transport-rxtx [maven-release-plugin] prepare for next development iteration 2014-10-29 11:48:40 +01:00
transport-sctp [maven-release-plugin] prepare for next development iteration 2014-10-29 11:48:40 +01:00
transport-udt Small performance improvements 2014-11-20 00:58:35 -05: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 Fix dependency issues with hamcrest 2014-12-04 18:00:02 +09:00
README.md Add a link to the 'native transports' page 2014-07-21 12:54:43 -07:00
run-example.sh Add logLevel property to enable different log levels for the examples. 2014-11-21 10:48:13 +09:00

README.md

Netty Project

Netty is an asynchronous event-driven network application framework for rapid development of maintainable high performance protocol servers & clients.

Links

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.