Go to file
Norman Maurer 870b5f5e4b Not add inboundStreamHandler for outbound streams created by Http2MultiplexCodec.
Motivation:

We must not add the inboundStreamHandler for outbound streams creates by Http2MultiplexCodec as the user will specify a handler via Http2StreamChannelBootstrap.

Modifications:

- Check if the stream is for outbound and if so not add the inboundStreamHandler to the pipeline
- Update tests so this is covered.

Result:

Fixes [#7178]
2017-09-06 08:37:29 +02:00
.github Use GitHub Issue/PR Template Feature 2016-12-07 11:40:26 -08:00
all [maven-release-plugin] prepare for next development iteration 2017-08-24 15:38:22 +02:00
bom [maven-release-plugin] prepare for next development iteration 2017-08-24 15:38:22 +02:00
buffer Allow to construct UnpooledByteBufAllocator that explictly always use sun.misc.Cleaner 2017-08-31 12:57:09 +02:00
codec Makes LengthFieldBasedFrameDecoder::decode inlineable 2017-08-28 09:08:45 +02:00
codec-dns [maven-release-plugin] prepare for next development iteration 2017-08-24 15:38:22 +02:00
codec-haproxy [maven-release-plugin] prepare for next development iteration 2017-08-24 15:38:22 +02:00
codec-http HttpObjectEncoder buffer size estimation 2017-08-31 01:40:53 -07:00
codec-http2 Not add inboundStreamHandler for outbound streams created by Http2MultiplexCodec. 2017-09-06 08:37:29 +02:00
codec-memcache [maven-release-plugin] prepare for next development iteration 2017-08-24 15:38:22 +02:00
codec-mqtt [maven-release-plugin] prepare for next development iteration 2017-08-24 15:38:22 +02:00
codec-redis [maven-release-plugin] prepare for next development iteration 2017-08-24 15:38:22 +02:00
codec-smtp [maven-release-plugin] prepare for next development iteration 2017-08-24 15:38:22 +02:00
codec-socks DefaultSocks5CommandRequest incorrectly rejects SOCKS5 commands with dstPort=0 2017-08-29 15:03:09 +02:00
codec-stomp Fix StompSubframeDecoder.readHeaders produce not any notification when parsed line that contains multiple colon 2017-08-29 22:06:45 +02:00
codec-xml [maven-release-plugin] prepare for next development iteration 2017-08-24 15:38:22 +02:00
common Only load native transport if running architecture match the compiled library architecture. 2017-09-04 13:34:55 +02:00
dev-tools [maven-release-plugin] prepare for next development iteration 2017-08-24 15:38:22 +02:00
example [maven-release-plugin] prepare for next development iteration 2017-08-24 15:38:22 +02:00
handler Only load native transport if running architecture match the compiled library architecture. 2017-09-04 13:34:55 +02:00
handler-proxy [maven-release-plugin] prepare for next development iteration 2017-08-24 15:38:22 +02:00
license Remove reference to akka code and ArrayDeque which is not part of netty anymore 2017-03-07 21:30:51 +01:00
microbench [maven-release-plugin] prepare for next development iteration 2017-08-24 15:38:22 +02:00
resolver [maven-release-plugin] prepare for next development iteration 2017-08-24 15:38:22 +02:00
resolver-dns [maven-release-plugin] prepare for next development iteration 2017-08-24 15:38:22 +02:00
tarball [maven-release-plugin] prepare for next development iteration 2017-08-24 15:38:22 +02:00
testsuite AutoClose behavior may infinite loop 2017-08-25 21:01:41 -07:00
testsuite-autobahn [maven-release-plugin] prepare for next development iteration 2017-08-24 15:38:22 +02:00
testsuite-osgi [maven-release-plugin] prepare for next development iteration 2017-08-24 15:38:22 +02:00
transport AutoClose behavior may infinite loop 2017-08-25 21:01:41 -07:00
transport-native-epoll Only load native transport if running architecture match the compiled library architecture. 2017-09-04 13:34:55 +02:00
transport-native-kqueue Only load native transport if running architecture match the compiled library architecture. 2017-09-04 13:34:55 +02:00
transport-native-unix-common [maven-release-plugin] prepare for next development iteration 2017-08-24 15:38:22 +02:00
transport-native-unix-common-tests [maven-release-plugin] prepare for next development iteration 2017-08-24 15:38:22 +02:00
transport-rxtx [maven-release-plugin] prepare for next development iteration 2017-08-24 15:38:22 +02:00
transport-sctp [maven-release-plugin] prepare for next development iteration 2017-08-24 15:38:22 +02:00
transport-udt [maven-release-plugin] prepare for next development iteration 2017-08-24 15:38:22 +02:00
.fbprefs Updated Find Bugs configuration 2009-03-04 10:33:09 +00:00
.gitignore Use shaded dependency on JCTools instead of copy and paste 2016-06-10 13:19:45 +02: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:13:58 +09:00
LICENSE.txt Relicensed to Apache License v2 2009-08-28 07:15:49 +00:00
NOTICE.txt Remove reference to akka code and ArrayDeque which is not part of netty anymore 2017-03-07 21:30:51 +01:00
pom.xml [maven-release-plugin] prepare for next development iteration 2017-08-24 15:38:22 +02:00
README.md Updating Branches to look section to match the current branching structure of the project 2016-03-10 22:08:01 +01:00
run-example.sh Add UptimeServer and adjust UptimeClient's code style. 2017-04-28 07:41:07 +02: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

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.