Skip to content
Netty project - an event-driven asynchronous network application framework
Java C Shell Groovy Protocol Buffer C++
Find file
Latest commit 467e5a1 Apr 28, 2016 @Scottmitch Scottmitch 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 #5186
Failed to load latest commit information.
all [maven-release-plugin] prepare for next development iteration Apr 10, 2016
buffer Add ByteBuf.asReadOnly() Apr 14, 2016
codec-dns Update dependencies Apr 14, 2016
codec-haproxy [maven-release-plugin] prepare for next development iteration Apr 10, 2016
codec-http TreeMap extra get operation removed. Apr 25, 2016
codec-http2 DefaultHttp2FrameReader stops reading if stream error Apr 30, 2016
codec-memcache [maven-release-plugin] prepare for next development iteration Apr 10, 2016
codec-mqtt [maven-release-plugin] prepare for next development iteration Apr 10, 2016
codec-redis Motivation: Apr 20, 2016
codec-smtp [maven-release-plugin] prepare for next development iteration Apr 10, 2016
codec-socks [maven-release-plugin] prepare for next development iteration Apr 10, 2016
codec-stomp [maven-release-plugin] prepare for next development iteration Apr 10, 2016
codec-xml Update dependencies Apr 14, 2016
codec Add ByteBuf.asReadOnly() Apr 14, 2016
common [maven-release-plugin] prepare for next development iteration Apr 10, 2016
example Add an example client for codec-redis Apr 23, 2016
handler-proxy [maven-release-plugin] prepare for next development iteration Apr 10, 2016
handler A new ChannelHandler that allows the user to control the flow of mess… Apr 23, 2016
license added support for Protobuf codec nano runtime Jan 19, 2016
microbench Update dependencies Apr 14, 2016
resolver-dns [maven-release-plugin] prepare for next development iteration Apr 10, 2016
resolver [maven-release-plugin] prepare for next development iteration Apr 10, 2016
tarball [maven-release-plugin] prepare for next development iteration Apr 10, 2016
testsuite-osgi [maven-release-plugin] prepare for next development iteration Apr 10, 2016
testsuite [maven-release-plugin] prepare for next development iteration Apr 10, 2016
transport-native-epoll EpollEventLoopGroup support Executor Apr 21, 2016
transport-rxtx [maven-release-plugin] prepare for next development iteration Apr 10, 2016
transport-sctp [maven-release-plugin] prepare for next development iteration Apr 10, 2016
transport-udt [maven-release-plugin] prepare for next development iteration Apr 10, 2016
transport NioEventLoop closes channel even if channel is not registered Apr 21, 2016
.fbprefs Updated Find Bugs configuration Mar 4, 2009
.gitignore Add JVM crash logs to .gitignore May 18, 2014
.travis.yml Travis CI branch whitelisting Mar 11, 2013
CONTRIBUTING.md Move the pull request guide to the developer guide Mar 12, 2014
LICENSE.txt Relicensed to Apache License v2 Aug 28, 2009
NOTICE.txt added support for Protobuf codec nano runtime Jan 19, 2016
README.md Updating Branches to look section to match the current branching stru… Mar 10, 2016
pom.xml Update dependencies Apr 14, 2016
run-example.sh Add an example client for codec-redis Apr 23, 2016

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.

Something went wrong with that request. Please try again.