Go to file
Heng Zhang b3e0e09a82
Distribue weight to children when closing stream (#11490)
Motivation:

As suggested in [section 5.3.4 in http2 spec](https://datatracker.ietf.org/doc/html/rfc7540#section-5.3.4):

> When a stream is removed from the dependency tree, its dependencies can be moved to become dependent on the parent of the closed stream. The weights of new dependencies are recalculated by distributing the weight of the dependency of the closed stream proportionally based on the weights of its dependencies.

For example, we have stream A and B depend on connection stream with default weights (16), and stream C depends on A with max weight (256). When stream A was closed, we move stream C to become dependent on the connection stream, then we should distribute the weight of stream A to its children (only stream C), so the new weight of stream C will be 16. If we keep the weight of stream C unchanged, it will get more resource than stream B

Modification:
- distribute weight to its children when closing a stream
- add a unit test for the case above and fix other related unit tests

Result:

More spec-compliant and more appropriate stream reprioritization

Co-authored-by: Heng Zhang <zhangheng@imo.im>
2021-07-20 14:17:56 +02:00
.github Revert "Only do a partial build for a few jobs when verify PRs (#11464)" 2021-07-13 15:32:42 +02:00
.mvn/wrapper Use MAVEN_OPTS to setup timeouts for dependency downloads (#11250) 2021-05-12 18:02:35 +02:00
all [maven-release-plugin] prepare for next development iteration 2021-07-16 06:23:23 +00:00
bom [maven-release-plugin] prepare for next development iteration 2021-07-16 06:23:23 +00:00
buffer [maven-release-plugin] prepare for next development iteration 2021-07-16 06:23:23 +00:00
codec [maven-release-plugin] prepare for next development iteration 2021-07-16 06:23:23 +00:00
codec-dns [maven-release-plugin] prepare for next development iteration 2021-07-16 06:23:23 +00:00
codec-haproxy [maven-release-plugin] prepare for next development iteration 2021-07-16 06:23:23 +00:00
codec-http [maven-release-plugin] prepare for next development iteration 2021-07-16 06:23:23 +00:00
codec-http2 Distribue weight to children when closing stream (#11490) 2021-07-20 14:17:56 +02:00
codec-memcache [maven-release-plugin] prepare for next development iteration 2021-07-16 06:23:23 +00:00
codec-mqtt [maven-release-plugin] prepare for next development iteration 2021-07-16 06:23:23 +00:00
codec-redis [maven-release-plugin] prepare for next development iteration 2021-07-16 06:23:23 +00:00
codec-smtp [maven-release-plugin] prepare for next development iteration 2021-07-16 06:23:23 +00:00
codec-socks [maven-release-plugin] prepare for next development iteration 2021-07-16 06:23:23 +00:00
codec-stomp [maven-release-plugin] prepare for next development iteration 2021-07-16 06:23:23 +00:00
codec-xml [maven-release-plugin] prepare for next development iteration 2021-07-16 06:23:23 +00:00
common [maven-release-plugin] prepare for next development iteration 2021-07-16 06:23:23 +00:00
dev-tools [maven-release-plugin] prepare for next development iteration 2021-07-16 06:23:23 +00:00
docker Revert "Only do a partial build for a few jobs when verify PRs (#11464)" 2021-07-13 15:32:42 +02:00
example [maven-release-plugin] prepare for next development iteration 2021-07-16 06:23:23 +00:00
handler [maven-release-plugin] prepare for next development iteration 2021-07-16 06:23:23 +00:00
handler-proxy [maven-release-plugin] prepare for next development iteration 2021-07-16 06:23:23 +00:00
license Introduce BrotliEncoder (#11256) 2021-07-08 11:51:27 +02:00
microbench [maven-release-plugin] prepare for next development iteration 2021-07-16 06:23:23 +00:00
resolver [maven-release-plugin] prepare for next development iteration 2021-07-16 06:23:23 +00:00
resolver-dns [maven-release-plugin] prepare for next development iteration 2021-07-16 06:23:23 +00:00
resolver-dns-native-macos [maven-release-plugin] prepare for next development iteration 2021-07-16 06:23:23 +00:00
scripts Remove tarball module (#11377) 2021-06-10 10:19:18 +02:00
testsuite [maven-release-plugin] prepare for next development iteration 2021-07-16 06:23:23 +00:00
testsuite-autobahn [maven-release-plugin] prepare for next development iteration 2021-07-16 06:23:23 +00:00
testsuite-http2 [maven-release-plugin] prepare for next development iteration 2021-07-16 06:23:23 +00:00
testsuite-native [maven-release-plugin] prepare for next development iteration 2021-07-16 06:23:23 +00:00
testsuite-native-image [maven-release-plugin] prepare for next development iteration 2021-07-16 06:23:23 +00:00
testsuite-native-image-client [maven-release-plugin] prepare for next development iteration 2021-07-16 06:23:23 +00:00
testsuite-native-image-client-runtime-init [maven-release-plugin] prepare for next development iteration 2021-07-16 06:23:23 +00:00
testsuite-osgi [maven-release-plugin] prepare for next development iteration 2021-07-16 06:23:23 +00:00
testsuite-shading [maven-release-plugin] prepare for next development iteration 2021-07-16 06:23:23 +00:00
transport [maven-release-plugin] prepare for next development iteration 2021-07-16 06:23:23 +00:00
transport-blockhound-tests [maven-release-plugin] prepare for next development iteration 2021-07-16 06:23:23 +00:00
transport-native-epoll [maven-release-plugin] prepare for next development iteration 2021-07-16 06:23:23 +00:00
transport-native-kqueue [maven-release-plugin] prepare for next development iteration 2021-07-16 06:23:23 +00:00
transport-native-unix-common [maven-release-plugin] prepare for next development iteration 2021-07-16 06:23:23 +00:00
transport-native-unix-common-tests [maven-release-plugin] prepare for next development iteration 2021-07-16 06:23:23 +00:00
transport-rxtx [maven-release-plugin] prepare for next development iteration 2021-07-16 06:23:23 +00:00
transport-sctp [maven-release-plugin] prepare for next development iteration 2021-07-16 06:23:23 +00:00
transport-udt [maven-release-plugin] prepare for next development iteration 2021-07-16 06:23:23 +00:00
.fbprefs Updated Find Bugs configuration 2009-03-04 10:33:09 +00:00
.gitattributes Include mvn wrapper to make setup of development env easier 2018-01-26 08:13:17 +01:00
.gitignore Ignore .shelf/ folder generated by IntelliJ IDEA (#10445) 2020-08-03 07:51:53 +02:00
.lgtm.yml Enables lgtm.com to process this project and create a CodeQL database 2020-01-17 11:05:53 +01:00
CONTRIBUTING.md Change the netty.io homepage scheme(http -> https) (#9344) 2019-07-09 21:09:42 +02:00
LICENSE.txt Enable nohttp check during the build (#10708) 2020-10-23 14:44:18 +02:00
mvnw Enable nohttp check during the build (#10708) 2020-10-23 14:44:18 +02:00
mvnw.cmd Enable nohttp check during the build (#10708) 2020-10-23 14:44:18 +02:00
nohttp-checkstyle-suppressions.xml Ensure Checkstyle suppression for dependency-reduced-pom.xml on Windows (#10899) 2021-01-01 19:30:13 +01:00
nohttp-checkstyle.xml Enable nohttp check during the build (#10708) 2020-10-23 14:44:18 +02:00
NOTICE.txt Introduce BrotliEncoder (#11256) 2021-07-08 11:51:27 +02:00
pom.xml [maven-release-plugin] prepare for next development iteration 2021-07-16 06:23:23 +00:00
README.md Fix url in README.md (#10915) 2021-01-11 07:48:58 +01:00
run-example.sh Add license header to our scripts and workflows (#11282) 2021-05-19 14:06:42 +02:00
SECURITY.md Added a security policy (#10692) 2020-10-15 20:39:37 +02:00

Build project

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+ / 4.1+) 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.1 resides in the branch '3.9' and the branch '4.1' 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.