Go to file
nmittler bfac74e382 Forking Twitter's hpack
Motivation:

The twitter hpack project does not have the support that it used to have.  See discussion here: https://github.com/netty/netty/issues/4403.

Modifications:

Created a new module in Netty and copied the latest from twitter hpack master.

Result:

Netty no longer depends on twitter hpack.
2015-11-14 10:12:49 -08:00
all Update Netty to latest netty-tcnative 2015-09-18 12:01:36 -07:00
buffer Export defaults from PooledByteBufAcclocator static fields 2015-11-08 08:08:33 +01:00
codec Improve the performance of copying header sets when hashing and name validation are equivalent. 2015-11-07 08:41:57 -08:00
codec-dns Provide more control over DnsNameResolver.query() / Add NameResolver.resolveAll() 2015-08-18 17:41:38 +09:00
codec-haproxy Add ProtocolDetectionResult and use it in HAProxyMessageDecoder for allow detect HAProxy protocol. 2015-06-23 08:59:16 +02:00
codec-http IllegalRefCountException in FullHttp[Request|Response].hashCode() 2015-11-09 16:51:42 -08:00
codec-http2 Forking Twitter's hpack 2015-11-14 10:12:49 -08:00
codec-memcache Fix a buffer leak in BinaryMemcacheEncoderTest 2015-08-29 11:55:33 +09:00
codec-mqtt Fix code styles on MQTT codec classes 2015-08-31 08:25:18 +02:00
codec-socks [maven-release-plugin] prepare for next development iteration 2015-03-03 08:30:59 -05:00
codec-stomp HTTP/2 Headers Type Updates 2015-10-30 14:33:48 -07:00
codec-xml [maven-release-plugin] prepare for next development iteration 2015-03-03 08:30:59 -05:00
common AsciiString optimized hashCode 2015-11-10 10:29:17 -08:00
example Remove HttpHeadersUtil 2015-11-09 12:03:32 -08:00
handler ApplicationProtocolNegotiationHandler failure behavior 2015-11-07 09:33:33 -08:00
handler-proxy ByteString introduced as AsciiString super class 2015-04-15 10:45:18 -07:00
license Forking Twitter's hpack 2015-11-14 10:12:49 -08:00
microbench Forking Twitter's hpack 2015-11-14 10:12:49 -08:00
resolver Provide more control over DnsNameResolver.query() / Add NameResolver.resolveAll() 2015-08-18 17:41:38 +09:00
resolver-dns Use separate query ID space for different DNS servers 2015-11-09 15:25:26 -08:00
tarball [maven-release-plugin] prepare for next development iteration 2015-03-03 08:30:59 -05:00
testsuite Remove HttpHeadersUtil 2015-11-09 12:03:32 -08:00
testsuite-osgi Add a property to disable osgi testsuite run 2015-08-13 09:52:46 +09:00
transport Improved DefaultChannelPipeline#destroy() to avoid spinning continuously in case of custom executors. 2015-11-06 19:38:07 +01:00
transport-native-epoll EPOLL Shutdown and Half Closed 2015-11-02 13:02:20 -08:00
transport-rxtx maxBytesPerRead channel configuration 2015-08-06 00:00:28 -07:00
transport-sctp [#4327] Ensure toString() will not throw IllegalReferenceCountException 2015-10-10 20:12:56 +02:00
transport-udt a48e5c7347 merge build failure 2015-08-06 10:28:39 -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 Forking Twitter's hpack 2015-11-14 10:12:49 -08:00
pom.xml Forking Twitter's hpack 2015-11-14 10:12:49 -08:00
README.md Fix the 'branches to look' section 2015-10-27 13:59:26 +01: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.