andreacavalli/netty5
1
0
Fork 0
Code Issues Pull Requests Projects Releases Wiki Activity
6,102 Commits 27 Branches 234 Tags 84 MiB
Java 99.8%
Shell 0.1%
4a3ef90381
Go to file
Norman Maurer 4a3ef90381 Port ChannelOutboundBuffer and related changes from 4.0 
Motivation:

We did various changes related to the ChannelOutboundBuffer in 4.0 branch. This commit port all of them over and so make sure our branches are synced in terms of these changes.

Related to [#2734], [#2709], [#2729], [#2710] and [#2693] .

Modification:
Port all changes that was done on the ChannelOutboundBuffer.

This includes the port of the following commits:
 - 73dfd7c01b
 - 997d8c32d2
 - e282e504f1
 - 5e5d1a58fd
 - 8ee3575e72
 - d6f0d12a86
 - 16e50765d1
 - 3f3e66c31a

Result:
 - Less memory usage by ChannelOutboundBuffer
 - Same code as in 4.0 branch
 - Make it possible to use ChannelOutboundBuffer with Channel implementation that not extends AbstractChannel
2014-08-05 15:00:56 +02:00
all Add MQTT protocol codec 2014-06-21 16:51:37 +09:00
buffer Port ChannelOutboundBuffer and related changes from 4.0 2014-08-05 15:00:56 +02:00
codec Improve Bzip2BitReader/Writer 2014-08-04 08:01:19 +02: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 [#2732] HttpRequestEncoder may produce invalid uri if uri parameters are included. 2014-08-05 10:14:06 +02:00
codec-http2 Remove compressed flag from HTTP/2 2014-07-23 19:47:11 +02: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 Fix most inspector warnings 2014-07-02 19:04:11 +09:00
codec-stomp Fix NPE problems 2014-07-20 12:55:08 +02:00
common Port ChannelOutboundBuffer and related changes from 4.0 2014-08-05 15:00:56 +02:00
example Fix a compilation error 2014-07-23 14:56:20 -07:00
handler Clean-up d9cccccbb3 2014-08-04 10:54:13 -07:00
license Implemented a Bzip2Encoder 2014-07-17 16:19:59 +02: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 [#2647] Respect IOV_MAX when call writev in native transport 2014-07-09 12:18:48 +02:00
transport Port ChannelOutboundBuffer and related changes from 4.0 2014-08-05 15:00:56 +02:00
transport-native-epoll Port ChannelOutboundBuffer and related changes from 4.0 2014-08-05 15:00:56 +02:00
transport-rxtx Fix most inspector warnings 2014-07-02 19:04:11 +09:00
transport-sctp Port ChannelOutboundBuffer and related changes from 4.0 2014-08-05 15:00:56 +02:00
transport-udt Port ChannelOutboundBuffer and related changes from 4.0 2014-08-05 15:00:56 +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:34:51 +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:17:58 +09:00
LICENSE.txt Relicensed to Apache License v2 2009-08-28 07:15:49 +00:00
NOTICE.txt Implemented a Bzip2Encoder 2014-07-17 16:19:59 +02:00
pom.xml Implemented LZF compression codec 2014-07-17 07:18:53 +02:00
README.md Add a link to the 'native transports' page 2014-07-21 12:10:16 -07:00
run-example.sh Overall refactoring of the STOMP codec 2014-06-04 17:09:11 +09: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.