Go to file
Scott Mitchell 9a63aafe22 EPOLL ET Set ReadFlag and Limit epollInReadyRunnable
Motivation:
441aa4c575 conditionally set the readFlag based upon if maybeMoreDataToRead is set. It is possible that the read flag will not be set, and nothing will be read by executeEpollInReadyRunnable and no actual data will be read even though the user requested it.

Modifications:
- Always set the readFlag in doBeginRead
- Make it so only a single epollInReadyRunnable can execute for a channel at a time

Result:
Less chance of missing read events in EPOLL transport.
2016-04-08 11:03:52 +02:00
all [maven-release-plugin] prepare for next development iteration 2016-04-02 01:25:05 -04:00
buffer Use Math.min(...) and Math.max(...) as these are intrinsics. 2016-04-06 21:30:32 +02:00
codec [maven-release-plugin] prepare for next development iteration 2016-04-02 01:25:05 -04:00
codec-dns Remove an unused import 2016-04-02 01:39:47 -04:00
codec-haproxy [maven-release-plugin] prepare for next development iteration 2016-04-02 01:25:05 -04:00
codec-http Propagate h2c upgrade success event to the next handler before removing source codec 2016-04-07 17:41:46 +02:00
codec-http2 [maven-release-plugin] prepare for next development iteration 2016-04-02 01:25:05 -04:00
codec-memcache Set the length fields of memcache messages automatically 2016-04-07 06:30:42 +02:00
codec-mqtt [maven-release-plugin] prepare for next development iteration 2016-04-02 01:25:05 -04:00
codec-smtp Add smtp codec (client side only). 2016-04-07 18:42:17 +02:00
codec-socks [maven-release-plugin] prepare for next development iteration 2016-04-02 01:25:05 -04:00
codec-stomp [maven-release-plugin] prepare for next development iteration 2016-04-02 01:25:05 -04:00
codec-xml [maven-release-plugin] prepare for next development iteration 2016-04-02 01:25:05 -04:00
common Make all InternalLoggerFactory implementations be singletons 2016-04-08 09:39:32 +02:00
example Set the length fields of memcache messages automatically 2016-04-07 06:30:42 +02:00
handler fcbeebf6df unit test bug 2016-04-06 00:11:10 -07:00
handler-proxy [maven-release-plugin] prepare for next development iteration 2016-04-02 01:25:05 -04:00
license added support for Protobuf codec nano runtime 2016-01-19 21:39:17 +01:00
microbench [maven-release-plugin] prepare for next development iteration 2016-04-02 01:25:05 -04:00
resolver [maven-release-plugin] prepare for next development iteration 2016-04-02 01:25:05 -04:00
resolver-dns [maven-release-plugin] prepare for next development iteration 2016-04-02 01:25:05 -04:00
tarball [maven-release-plugin] prepare for next development iteration 2016-04-02 01:25:05 -04:00
testsuite Make OIO/NIO/EPOLL autoReadClear consistent 2016-04-06 12:32:14 -07:00
testsuite-osgi [maven-release-plugin] prepare for next development iteration 2016-04-02 01:25:05 -04:00
transport Fix checkstyle 2016-04-08 17:44:52 +09:00
transport-native-epoll EPOLL ET Set ReadFlag and Limit epollInReadyRunnable 2016-04-08 11:03:52 +02:00
transport-rxtx [maven-release-plugin] prepare for next development iteration 2016-04-02 01:25:05 -04:00
transport-sctp Make OIO/NIO/EPOLL autoReadClear consistent 2016-04-06 12:32:14 -07:00
transport-udt [maven-release-plugin] prepare for next development iteration 2016-04-02 01:25:05 -04: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 added support for Protobuf codec nano runtime 2016-01-19 21:39:17 +01:00
pom.xml Add smtp codec (client side only). 2016-04-07 18:42:17 +02:00
README.md Updating Branches to look section to match the current branching structure of the project 2016-03-10 22:08:01 +01:00
run-example.sh Map HTTP/2 Streams to Channels 2016-03-25 12:14:44 -07: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

Development of all 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.