Go to file
Jakob Buchgraber e3980a6487 Http2ConnectionHandler should propagate channelActive and channelInactive events.
Motivation:

The Http2ConnectionHandler incorrectly doesn't propagate channelActive and channelInactive events and thus breaks the pipeline
for other ChannelHandler.

Modification:

- Add calls to super.channelActive() and super.channelInactive().
- Remove unused methods.

Result:

- Http2ConnectionHandler can be used with other ChannelHandlers.
2015-04-28 20:11:12 -07:00
all [maven-release-plugin] prepare for next development iteration 2015-03-03 08:30:59 -05:00
buffer ByteString arrayOffset method 2015-04-24 18:54:19 -07:00
codec fix the discardedBytes counting on LineBasedFrameDecoder 2015-04-21 09:13:54 +02:00
codec-dns [maven-release-plugin] prepare for next development iteration 2015-03-03 08:30:59 -05:00
codec-haproxy ByteString introduced as AsciiString super class 2015-04-15 10:45:18 -07:00
codec-http ByteString arrayOffset master branch cleanup 2015-04-25 14:24:39 -07:00
codec-http2 Http2ConnectionHandler should propagate channelActive and channelInactive events. 2015-04-28 20:11:12 -07:00
codec-memcache Returns after encoding each message not do check following instance types 2015-03-19 20:43:10 +01:00
codec-mqtt [maven-release-plugin] prepare for next development iteration 2015-03-03 08:30:59 -05:00
codec-socks [maven-release-plugin] prepare for next development iteration 2015-03-03 08:30:59 -05:00
codec-stomp ByteString introduced as AsciiString super class 2015-04-15 10:45:18 -07:00
codec-xml [maven-release-plugin] prepare for next development iteration 2015-03-03 08:30:59 -05:00
common [#3680] Enabled SecurityManager results in ClassNotFoundError during io.netty.util.NetUtil initialization 2015-04-27 20:02:16 +02:00
example ByteString introduced as AsciiString super class 2015-04-15 10:45:18 -07:00
handler Fix SslContextBuilder swapping client and server 2015-04-20 17:25:39 -07:00
handler-proxy ByteString introduced as AsciiString super class 2015-04-15 10:45:18 -07:00
license Integrate non-blocking XML parser as Netty codec (#2806) 2015-02-19 14:17:17 +01:00
microbench ByteString arrayOffset method 2015-04-24 18:54:19 -07:00
resolver Use InetSocketAddress.getHostName() instead of getHostString() 2015-03-10 11:45:56 +09:00
resolver-dns [maven-release-plugin] prepare for next development iteration 2015-03-03 08:30:59 -05:00
tarball [maven-release-plugin] prepare for next development iteration 2015-03-03 08:30:59 -05:00
testsuite Correctly test for non-auto-read correctness in testsuite 2015-04-20 10:15:41 +02:00
testsuite-osgi [maven-release-plugin] prepare for next development iteration 2015-03-03 08:30:59 -05:00
transport [#3662] Fail the connect future on close 2015-04-27 20:05:26 +02:00
transport-native-epoll [#3662] Fail the connect future on close 2015-04-27 20:05:26 +02:00
transport-rxtx [maven-release-plugin] prepare for next development iteration 2015-03-03 08:30:59 -05:00
transport-sctp [maven-release-plugin] prepare for next development iteration 2015-03-03 08:30:59 -05:00
transport-udt Motivation: If there are no readable bytes, it's unnecessary to go through javaChannel().write(). 2015-04-08 09:35:33 +02: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 Integrate non-blocking XML parser as Netty codec (#2806) 2015-02-19 14:17:17 +01:00
pom.xml Add support for ALPN when using openssl + NPN client mode and support for CipherSuiteFilter 2015-04-10 18:34:09 +02:00
README.md Add a link to the 'native transports' page 2014-07-21 12:10:16 -07:00
run-example.sh Add logLevel property to enable different log levels for the examples. 2014-11-21 10:49:27 +09:00

Netty Project

Netty is an asynchronous event-driven network application framework for rapid development of maintainable high performance protocol servers & clients.

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.