Go to file
Scott Mitchell 467e5a1019 DefaultHttp2FrameReader stops reading if stream error
Motivation:
DefaultHttp2FrameReader will stop reading data if any exception is thrown. However some exceptions are recoverable and we will lose data if we don't continue reading. For example some stream errors are recoverable.

Modifications:
- DefaultHttp2FrameReader should attempt to continue reading if a stream error is encountered.

Result:
Fixes https://github.com/netty/netty/issues/5186
2016-04-30 10:41:06 -07:00
all [maven-release-plugin] prepare for next development iteration 2016-04-10 08:37:18 +02:00
buffer Add ByteBuf.asReadOnly() 2016-04-14 10:51:20 +02:00
codec Add ByteBuf.asReadOnly() 2016-04-14 10:51:20 +02:00
codec-dns Update dependencies 2016-04-14 11:05:53 +02:00
codec-haproxy [maven-release-plugin] prepare for next development iteration 2016-04-10 08:37:18 +02:00
codec-http TreeMap extra get operation removed. 2016-04-25 09:49:05 -07:00
codec-http2 DefaultHttp2FrameReader stops reading if stream error 2016-04-30 10:41:06 -07:00
codec-memcache [maven-release-plugin] prepare for next development iteration 2016-04-10 08:37:18 +02:00
codec-mqtt [maven-release-plugin] prepare for next development iteration 2016-04-10 08:37:18 +02:00
codec-redis Motivation: 2016-04-20 11:07:48 -07:00
codec-smtp [maven-release-plugin] prepare for next development iteration 2016-04-10 08:37:18 +02:00
codec-socks [maven-release-plugin] prepare for next development iteration 2016-04-10 08:37:18 +02:00
codec-stomp [maven-release-plugin] prepare for next development iteration 2016-04-10 08:37:18 +02:00
codec-xml Update dependencies 2016-04-14 11:05:53 +02:00
common [maven-release-plugin] prepare for next development iteration 2016-04-10 08:37:18 +02:00
example Add an example client for codec-redis 2016-04-23 11:18:12 -07:00
handler A new ChannelHandler that allows the user to control the flow of messages if upstream handlers emit more than one event for each read() 2016-04-23 11:13:12 -07:00
handler-proxy [maven-release-plugin] prepare for next development iteration 2016-04-10 08:37:18 +02:00
license added support for Protobuf codec nano runtime 2016-01-19 21:39:17 +01:00
microbench Update dependencies 2016-04-14 11:05:53 +02:00
resolver [maven-release-plugin] prepare for next development iteration 2016-04-10 08:37:18 +02:00
resolver-dns [maven-release-plugin] prepare for next development iteration 2016-04-10 08:37:18 +02:00
tarball [maven-release-plugin] prepare for next development iteration 2016-04-10 08:37:18 +02:00
testsuite [maven-release-plugin] prepare for next development iteration 2016-04-10 08:37:18 +02:00
testsuite-osgi [maven-release-plugin] prepare for next development iteration 2016-04-10 08:37:18 +02:00
transport NioEventLoop closes channel even if channel is not registered 2016-04-21 09:17:14 -07:00
transport-native-epoll EpollEventLoopGroup support Executor 2016-04-21 08:33:49 -07:00
transport-rxtx [maven-release-plugin] prepare for next development iteration 2016-04-10 08:37:18 +02:00
transport-sctp [maven-release-plugin] prepare for next development iteration 2016-04-10 08:37:18 +02:00
transport-udt [maven-release-plugin] prepare for next development iteration 2016-04-10 08:37:18 +02: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:36:54 +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:13:58 +09:00
LICENSE.txt Relicensed to Apache License v2 2009-08-28 07:15:49 +00:00
NOTICE.txt added support for Protobuf codec nano runtime 2016-01-19 21:39:17 +01:00
pom.xml Update dependencies 2016-04-14 11:05:53 +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 an example client for codec-redis 2016-04-23 11:18:12 -07: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.