andreacavalli/netty5
1
0
Fork 0
Code Issues Pull Requests Projects Releases Wiki Activity
5,879 Commits 27 Branches 234 Tags 84 MiB
Java 99.8%
Shell 0.1%
d9d906c54e
Go to file
Norman Maurer d9d906c54e Reuse previous created HttpHeaders by HttpObjectAggregator 
Motivation:

HttpObjectAggregator currently creates a new FullHttpResponse / FullHttpRequest for each message it needs to aggregate. While doing so it also creates 2 DefaultHttpHeader instances (one for the headers and one for the trailing headers). This is bad for two reasons:
  - More objects are created then needed and also populate the headers is not for free
  - Headers may get validated even if the validation was disabled in the decoder

Modification:

- Wrap the previous created HttpResponse / HttpRequest and so reuse the original HttpHeaders
- Reuse the previous created trailing HttpHeader.
- Fix a bug where the trailing HttpHeader was incorrectly mixed in the headers.

Result:

- Less GC
- Faster HttpObjectAggregator implementation
2014-07-11 06:41:03 +02:00
all [maven-release-plugin] prepare for next development iteration 2014-06-30 14:31:08 +02:00
buffer [#2642] CompositeByteBuf.deallocate memory/GC improvement 2014-07-08 21:08:34 +02:00
codec [#2643] Throw TooLongFrameException instead of using fireExceptionCaught 2014-07-10 06:57:08 +02:00
codec-http Reuse previous created HttpHeaders by HttpObjectAggregator 2014-07-11 06:41:03 +02:00
codec-socks Fix most inspector warnings 2014-07-02 20:21:30 +09:00
common Log the time taken for generating the initialSeedUniquifier 2014-07-04 13:27:18 +09:00
example Move generic code to HttpOrSpdyChooser to simplify implementations 2014-07-07 09:34:33 +02:00
handler Fix most inspector warnings 2014-07-02 20:21:30 +09:00
license Preparation for porting OpenSSL support in 3.10 2014-05-17 20:01:47 +09:00
microbench [maven-release-plugin] prepare for next development iteration 2014-06-30 14:31:08 +02:00
tarball [maven-release-plugin] prepare for next development iteration 2014-06-30 14:31:08 +02:00
testsuite [#2647] Respect IOV_MAX when call writev in native transport 2014-07-09 13:32:43 +02:00
transport [#2644] Correctly release buffer when exception happens during send DatagramPacket or SctpMessage 2014-07-08 20:15:33 +02:00
transport-native-epoll [#2647] Respect IOV_MAX when call writev in native transport 2014-07-09 13:32:43 +02:00
transport-rxtx Fix most inspector warnings 2014-07-02 20:21:30 +09:00
transport-sctp [#2644] Correctly release buffer when exception happens during send DatagramPacket or SctpMessage 2014-07-08 20:15:33 +02:00
transport-udt Fix most inspector warnings 2014-07-02 20:21:30 +09: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 Preparation for porting OpenSSL support in 3.10 2014-05-17 20:01:47 +09:00
pom.xml Add missing m2eclipse life cycle mapping 2014-07-06 16:53:53 +09:00
README.md Update README.md 2014-01-16 14:38:36 +09:00
run-example.sh Use a forked exec-maven-plugin instead of maven-antrun-plugin 2014-05-23 20:06:12 +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.