andreacavalli/netty5
1
0
Fork 0
Code Issues Pull Requests Projects Releases Wiki Activity
9,065 Commits 27 Branches 234 Tags 84 MiB
Java 99.8%
Shell 0.1%
a0c3081d82
Go to file
Nick Hill a0c3081d82 Reduce http2 buffer slicing (#8598) 
Motivation

DefaultHttp2FrameReader currently does a fair amount of "intermediate"
slicing which can be avoided.

Modifications

Avoid slicing the input buffer in DefaultHttp2FrameReader until
necessary. In one instance this also means retainedSlice can be used
instead (which may also avoid allocating).

Results

Less allocations when using http2.
2018-11-29 19:45:52 +01:00
.github
.mvn/wrapper
all
bom
buffer
codec
codec-dns
codec-haproxy
codec-http
codec-http2
codec-memcache
codec-mqtt
codec-redis
codec-smtp
codec-socks
codec-stomp
codec-xml
common
dev-tools
docker
example
handler
handler-proxy
license
microbench
resolver
resolver-dns
tarball
testsuite
testsuite-autobahn
testsuite-http2
testsuite-osgi
testsuite-shading
transport
transport-native-epoll
transport-native-kqueue
transport-native-unix-common
transport-native-unix-common-tests
transport-rxtx
transport-sctp
transport-udt
.fbprefs
.gitattributes
.gitignore
CONTRIBUTING.md
LICENSE.txt
mvnw
mvnw.cmd
NOTICE.txt
pom.xml
README.md
run-example.sh

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

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.

Usage with JDK 9

Netty can be used in modular JDK9 applications as a collection of automatic modules. The module names follow the reverse-DNS style, and are derived from subproject names rather than root packages due to historical reasons. They are listed below:

  • io.netty.all
  • io.netty.buffer
  • io.netty.codec
  • io.netty.codec.dns
  • io.netty.codec.haproxy
  • io.netty.codec.http
  • io.netty.codec.http2
  • io.netty.codec.memcache
  • io.netty.codec.mqtt
  • io.netty.codec.redis
  • io.netty.codec.smtp
  • io.netty.codec.socks
  • io.netty.codec.stomp
  • io.netty.codec.xml
  • io.netty.common
  • io.netty.handler
  • io.netty.handler.proxy
  • io.netty.resolver
  • io.netty.resolver.dns
  • io.netty.transport
  • io.netty.transport.epoll (native omitted - reserved keyword in Java)
  • io.netty.transport.kqueue (native omitted - reserved keyword in Java)
  • io.netty.transport.unix.common (native omitted - reserved keyword in Java)
  • io.netty.transport.rxtx
  • io.netty.transport.sctp
  • io.netty.transport.udt

Automatic modules do not provide any means to declare dependencies, so you need to list each used module separately in your module-info file.