d79e5c594d
Motivation: The API documentation in ChannelConfig states that a a channel is writable, if the number of pending bytes is below the low watermark and a channel is not writable, if the number of pending bytes exceeds the high watermark. Therefore, we should use < operators instead of <= as well as > instead of >=. Using <= and >= is also problematic, if the low watermark is equal to the high watermark, as then a channel could be both writable and unwritable with the same number of pending bytes (depending on whether remove() or addMessage() is called first). The use of <= and >= was introduced in PR https://github.com/netty/netty/pull/3036, but I don't understand why, as there doesn't seem to have been any discussion around that. Modifications: Use < and > operators instead of <= and >=. Result: High and low watermarks are treated as stated in the API docs. |
||
|---|---|---|
| all | ||
| buffer | ||
| codec | ||
| codec-haproxy | ||
| codec-http | ||
| codec-socks | ||
| common | ||
| example | ||
| handler | ||
| license | ||
| microbench | ||
| tarball | ||
| testsuite | ||
| testsuite-osgi | ||
| transport | ||
| transport-native-epoll | ||
| transport-rxtx | ||
| transport-sctp | ||
| transport-udt | ||
| .fbprefs | ||
| .gitignore | ||
| .travis.yml | ||
| CONTRIBUTING.md | ||
| LICENSE.txt | ||
| NOTICE.txt | ||
| pom.xml | ||
| README.md | ||
| run-example.sh | ||
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:
- Latest stable Oracle JDK 7
- Latest stable Apache Maven
- If you are on Linux, you need additional development packages installed on your system, because you'll build the native transport.
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.