andreacavalli/netty5
1
0
Fork 0
Code Issues Pull Requests Projects Releases Wiki Activity
6,189 Commits 27 Branches 234 Tags 84 MiB
Java 99.8%
Shell 0.1%
d35ddf0648
Go to file
nmittler d35ddf0648 Fixing queuing bug in outbound flow control. 
Motivation:

Outbound flow control does not properly remove the head of queue after
it's written. This will cause streams with multiple frames to get stuck
and not send all of the data.

Modifications:

Modified the DefaultHttp2OutboundFlowController to properly remove the
head of the pending write queue once a queued frame has been written.

Added an integration test that sends a large message to verify that all
DATA frames are properly collected at the other end.

Result:

Outbound flow control properly handles several queued messages.
2014-09-05 15:05:55 -07:00
all Add HTTP/2 codec to netty-all maven dependency Motivation: 2014-08-18 19:07:49 +02:00
buffer [#2843] Add test-case to show correct behavior of ByteBuf.refCnt() and ByteBuf.release(...) 2014-09-01 08:50:30 +02:00
codec HTTP/2 to HTTP priority translation 2014-08-26 14:06:02 -07:00
codec-dns Fix buffer leaks in DnsResponseDecoder and DnsResponseDecoderTest 2014-08-04 14:05:02 +02:00
codec-haproxy Fix NPE problems 2014-07-20 12:55:08 +02:00
codec-http [#2847] Correctly encode HTTP to SPDY if X-SPDY-Associated-To-Stream-ID is not present 2014-08-31 21:08:25 +02:00
codec-http2 Fixing queuing bug in outbound flow control. 2014-09-05 15:05:55 -07:00
codec-memcache Fix most inspector warnings 2014-07-02 19:04:11 +09:00
codec-mqtt Fix NPE problems 2014-07-20 12:55:08 +02:00
codec-socks codec-socks test cleanup 2014-08-20 06:54:55 +02:00
codec-stomp Fix a resource leak in StompSubframeAggregatorTest 2014-08-11 10:46:17 -07:00
common Fixing queuing bug in outbound flow control. 2014-09-05 15:05:55 -07:00
example ALPN java implementation 2014-08-30 13:41:07 -04:00
handler ALPN java implementation 2014-08-30 13:41:07 -04:00
license Implemented LZ4 compression codec 2014-08-14 15:05:57 -07:00
microbench Fix the inconsistencies between performance tests in ByteBufAllocatorBenchmark 2014-06-21 13:27:28 +09:00
tarball [maven-release-plugin] prepare for next development iteration 2013-12-22 22:06:15 +09:00
testsuite Better fix for TrafficShapingHandlerTest 2014-08-16 18:08:43 +02:00
transport Reset interrupted flag in SingleThreadEventLoopTest. Fixes #2841 2014-09-01 16:33:15 +02:00
transport-native-epoll [#2823] Writing DefaultFileRegion with EpollSocketChannel may cause hang 2014-08-26 15:09:27 +02: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 Make Nio/EpollEventLoop run on a ForkJoinPool 2014-08-11 15:28:46 -07: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 LZ4 compression codec 2014-08-14 15:05:57 -07:00
pom.xml ALPN java implementation 2014-08-30 13:41:07 -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.