Go to file
Scott Mitchell 4cac79594c Update HTTP/2 to RFCs
Motivation:
HTTP/2 RFC 7540 has been released.

Modifications:
- Make changes RFC 7540 introduced since draft 17.

Result:
HTTP/2 RFC 7540 compliant code
2015-05-26 16:08:26 -07:00
all [maven-release-plugin] prepare for next development iteration 2015-03-03 08:30:59 -05:00
buffer Expose metrics for PooledByteBufAllocator 2015-05-20 21:06:48 +02:00
codec Remove memory copy when extract frame in LengthFieldBasedFrameDecoder 2015-04-29 08:43:21 +02:00
codec-dns Fix missing ResourceLeak.close() in AbstractDnsMessage 2015-05-04 12:07:59 +09:00
codec-haproxy ByteString introduced as AsciiString super class 2015-04-15 10:45:18 -07:00
codec-http Support empty http responses when using compression 2015-05-26 09:36:00 +02:00
codec-http2 Update HTTP/2 to RFCs 2015-05-26 16:08:26 -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 [#3805] Fix incorrect javadoc in PlatformDependent 2015-05-25 21:42:45 +02:00
example SCTP echo client/server multi-homing examples 2015-05-22 22:23:48 +02:00
handler Allow writing with void promise if IdleStateHandler is configured in pipeline. 2015-05-25 21:08:02 +02: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 Have Http2LocalFlowController.consumeBytes indicate whether a WINDOW_UPDATE was written 2015-05-04 13:21:53 -07:00
resolver Use InetSocketAddress.getHostName() instead of getHostString() 2015-03-10 11:45:56 +09:00
resolver-dns Revamp DNS codec 2015-05-01 11:34:52 +09:00
tarball [maven-release-plugin] prepare for next development iteration 2015-03-03 08:30:59 -05:00
testsuite Fix compile error introduced by cherry-pick edf1eb10d5 2015-05-07 18:43:12 +02:00
testsuite-osgi Upgrade twitter hpack dependency 2015-04-30 17:14:33 -07:00
transport Not try to write more then Integer.MAX_VALUE / SSIZE_MAX via writev 2015-05-21 12:02:44 +02:00
transport-native-epoll Not try to write more then Integer.MAX_VALUE / SSIZE_MAX via writev 2015-05-21 12:02:44 +02:00
transport-rxtx [maven-release-plugin] prepare for next development iteration 2015-03-03 08:30:59 -05:00
transport-sctp Add support for SCTP 'unordered' flag. 2015-04-30 08:46:34 +02:00
transport-udt Remove duplicated code in AcceptorChannel classes. 2015-05-07 06:32:13 +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 Upgrading Jetty alpn-api version 2015-05-22 13:12:31 -07:00
README.md Add a link to the 'native transports' page 2014-07-21 12:10:16 -07:00
run-example.sh Add HTTP/2 Netty tiles example 2015-05-18 14:17:48 -07: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.