andreacavalli/netty5
1
0
Fork 0
Code Issues Pull Requests Projects Releases Wiki Activity
6,327 Commits 27 Branches 234 Tags 84 MiB
Java 99.8%
Shell 0.1%
1079d02ef5
Go to file
nmittler 1079d02ef5 HTTP/2 inbound flow controller always throws connection error 
Motivation:
When the inbound flow controller recognizes that the flow control window
has been violated on a stream (not connection-wide), it throws a
connection error.

Modifications:
Changed the DefaultHttp2InboundFlowController to properly throw
connection error if the connection window is violated and stream error
if a stream window is violated.

Result:
inbound flow control throws the correct error for window violations.
2014-11-19 09:50:44 -08:00
all Fix missing version properties of transport-epoll in all-in-one JAR 2014-10-21 22:36:19 +09:00
buffer Disable caching of PooledByteBuf for different threads. 2014-09-22 13:39:42 +02:00
codec Revert bad renaming in ZlibTest 2014-11-19 18:36:52 +09:00
codec-dns Add EDNS support to DnsQueryEncoder 2014-10-16 17:06:20 +09:00
codec-haproxy Fix NPE problems 2014-07-20 12:55:08 +02:00
codec-http SPDY: add support for pushed resources in SpdyHttpDecoder 2014-11-15 21:47:43 +01:00
codec-http2 HTTP/2 inbound flow controller always throws connection error 2014-11-19 09:50:44 -08:00
codec-memcache Add proxy support for client socket connections 2014-10-14 12:40:33 +09:00
codec-mqtt Add supporting MQTT 3.1.1 2014-11-15 09:07:56 +01:00
codec-socks Add proxy support for client socket connections 2014-10-14 12:40:33 +09:00
codec-stomp Netty Headers Class Restructure and Algorithm Updates 2014-10-21 13:04:08 -04:00
common Fix bug in HTTP/2 outbound flow control 2014-11-13 14:40:55 -08:00
example HTTP/2 Rename HTTP to HTTP2 object write converter 2014-11-19 08:58:47 -05:00
handler Add ApplicationProtocolConfig.DISABLED 2014-10-31 14:14:10 +09:00
handler-proxy Replace HttpHeaders.Names/Values with HttpHeaderNames/Values 2014-11-01 02:41:56 +09:00
license Implemented LZMA frame encoder 2014-09-15 15:14:15 +02:00
microbench Benchmark for HttpRequestDecoder 2014-11-12 14:20:38 +01:00
resolver Name resolver API and DNS-based name resolver 2014-10-16 17:10:36 +09:00
resolver-dns Improve DnsNameResolverTest.testResolveA() 2014-10-25 17:29:59 +09:00
tarball [maven-release-plugin] prepare for next development iteration 2013-12-22 22:06:15 +09:00
testsuite Replace HttpHeaders.Names/Values with HttpHeaderNames/Values 2014-11-01 02:41:56 +09:00
transport Correctly shutdown wrapped Executor in PausableChannelEventExecutor.shutdown() 2014-11-12 13:53:29 +01:00
transport-native-epoll Name resolver API and DNS-based name resolver 2014-10-16 17:10:36 +09:00
transport-rxtx Fix most inspector warnings 2014-07-02 19:04:11 +09:00
transport-sctp Allow to obtain RecvByteBufAllocator.Handle to allow more flexible implementations 2014-08-12 06:54:29 +02:00
transport-udt Name resolver API and DNS-based name resolver 2014-10-16 17:10:36 +09:00
.fbprefs Updated Find Bugs configuration 2009-03-04 10:33:09 +00:00
.gitignore Exclude bin directory from git Motivation: 2014-08-27 06:33:22 +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:17:58 +09:00
LICENSE.txt Relicensed to Apache License v2 2009-08-28 07:15:49 +00:00
NOTICE.txt Implemented LZMA frame encoder 2014-09-15 15:14:15 +02:00
pom.xml ALPN should allow handshake failure if no compatible protocols found 2014-10-30 19:39:31 -04:00
README.md Add a link to the 'native transports' page 2014-07-21 12:10:16 -07:00
run-example.sh ALPN java implementation 2014-08-30 13:41:07 -04:00

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

The 'master' branch is where the development of the latest major version lives on. The development of all other 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.