Go to file
Idel Pivnitskiy cc97be6002 Rewrite HttpObjectDecoder to make use of proper state machine
Motivation:

HttpObjectDecoder extended ReplayDecoder which is slightly slower then ByteToMessageDecoder.

Modifications:

- Changed super class of HttpObjectDecoder from ReplayDecoder to ByteToMessageDecoder.
- Rewrote decode() method of HttpObjectDecoder to use proper state machine.
- Changed private methods HeaderParser.parse(ByteBuf), readHeaders(ByteBuf) and readTrailingHeaders(ByteBuf), skipControlCharacters(ByteBuf) to consider available bytes.
- Set HeaderParser and LineParser as static inner classes.
- Replaced not safe actualReadableBytes() with buffer.readableBytes().

Result:

Improved performance of HttpObjectDecoder by approximately 177%.
2014-11-12 14:36:56 +01:00
all [maven-release-plugin] prepare for next development iteration 2014-10-29 11:48:40 +01:00
buffer [maven-release-plugin] prepare for next development iteration 2014-10-29 11:48:40 +01:00
codec HTTP Content Encoder allow EmptyLastHttpContent 2014-11-05 23:23:21 -05:00
codec-http Rewrite HttpObjectDecoder to make use of proper state machine 2014-11-12 14:36:56 +01:00
codec-socks [maven-release-plugin] prepare for next development iteration 2014-10-29 11:48:40 +01:00
common Handle the interface name in IPv6 address correctly 2014-11-12 12:15:14 +09:00
example Backport ALPN and Mutual Auth SSL 2014-10-31 14:15:12 +09:00
handler Add ApplicationProtocolConfig.DISABLED 2014-10-31 14:15:43 +09:00
license Remove license of deque as we not use it anymore 2014-08-04 12:21:33 +02:00
microbench [maven-release-plugin] prepare for next development iteration 2014-10-29 11:48:40 +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 Add generic versions of PromiseAggregator and PromiseNotifier. 2014-11-07 08:44:20 +01: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 [maven-release-plugin] prepare for next development iteration 2014-10-29 11:48:40 +01: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 build errors introduced during backporting SslContext 2014-10-31 14:25:14 +09:00
README.md Add a link to the 'native transports' page 2014-07-21 12:54:43 -07:00
run-example.sh Use a forked exec-maven-plugin instead of maven-antrun-plugin 2014-05-23 20:06:12 +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 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.