andreacavalli/netty5
1
0
Fork 0
Code Issues Pull Requests Projects Releases Wiki Activity
7,364 Commits 27 Branches 234 Tags 84 MiB
Java 99.8%
Shell 0.1%
01ab204ae5
Go to file
Norman Maurer 01ab204ae5 Revert "Not add ChannelHandler to ChannelPipeline once the pipeline was destroyed." 
This reverts commit 4cc98134da.
2017-06-08 19:51:02 +02:00
.github Use GitHub Issue/PR Template Feature 2016-12-07 11:40:46 -08:00
all Correctly exclude netty-tcnative classes from the all jar. 2017-05-30 16:01:19 -07:00
bom Correctly include native modules 2017-05-18 07:07:34 +02:00
buffer Allow to access memoryAddress of wrapped ByteBuf for ReadOnlyByteBuf 2017-06-07 18:45:40 +02:00
codec JdkZlibDecoder and JZlibDecoder consistency 2017-06-06 14:19:09 -07:00
codec-haproxy Added PROXY Protocol TLV support 2017-06-07 09:14:52 -07:00
codec-http Move QueryStringDecoder.decodeHexByte into ByteBufUtil 2017-06-07 09:32:01 -07:00
codec-socks [maven-release-plugin] prepare for next development iteration 2017-05-11 12:26:35 +02:00
common Use FQCN to prevent classloader issues on java6 2017-06-08 12:04:38 +02:00
dev-tools [maven-release-plugin] prepare for next development iteration 2017-05-11 12:26:35 +02:00
example [maven-release-plugin] prepare for next development iteration 2017-05-11 12:26:35 +02:00
handler OpenSslEngine return NEED_WRAP if the destination buffered filled 2017-06-02 07:47:57 -07:00
license Remove reference to akka code and ArrayDeque which is not part of netty anymore 2017-03-07 21:32:36 +01:00
microbench Optimizations in NetUtil 2017-05-18 16:51:44 -07:00
tarball [maven-release-plugin] prepare for next development iteration 2017-05-11 12:26:35 +02:00
testsuite Correctly handle ByteBuf implementations which have no memoryAddress when writing to native transport 2017-06-07 20:05:16 +02:00
testsuite-autobahn [maven-release-plugin] prepare for next development iteration 2017-05-11 12:26:35 +02:00
testsuite-osgi [maven-release-plugin] prepare for next development iteration 2017-05-11 12:26:35 +02:00
transport Revert "Not add ChannelHandler to ChannelPipeline once the pipeline was destroyed." 2017-06-08 19:51:02 +02:00
transport-native-epoll Correctly handle ByteBuf implementations which have no memoryAddress when writing to native transport 2017-06-07 20:05:16 +02:00
transport-rxtx [maven-release-plugin] prepare for next development iteration 2017-05-11 12:26:35 +02:00
transport-sctp Fix parameter order in SctpOutboundByteStreamHandler. 2017-05-25 09:29:58 +02:00
transport-udt [maven-release-plugin] prepare for next development iteration 2017-05-11 12:26:35 +02:00
.fbprefs Updated Find Bugs configuration 2009-03-04 10:33:09 +00:00
.gitignore Use shaded dependency on JCTools instead of copy and paste 2016-06-10 13:53:28 +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:18:14 +09:00
LICENSE.txt Relicensed to Apache License v2 2009-08-28 07:15:49 +00:00
NOTICE.txt Remove reference to akka code and ArrayDeque which is not part of netty anymore 2017-03-07 21:32:36 +01:00
pom.xml Update to latest netty-tcnative release 2017-06-07 20:06:42 +02:00
README.md Updating Branches to look section to match the current branching structure of the project 2016-03-10 22:09:30 +01:00
run-example.sh Add UptimeServer and adjust UptimeClient's code style. 2017-04-28 07:50:53 +02: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

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.