Go to file
nmittler 8accc52b03 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:13:32 -08:00
all [maven-release-plugin] prepare for next development iteration 2015-11-10 22:59:33 +01:00
buffer [maven-release-plugin] prepare for next development iteration 2015-11-10 22:59:33 +01:00
codec [maven-release-plugin] prepare for next development iteration 2015-11-10 22:59:33 +01:00
codec-dns [maven-release-plugin] prepare for next development iteration 2015-11-10 22:59:33 +01:00
codec-haproxy [maven-release-plugin] prepare for next development iteration 2015-11-10 22:59:33 +01:00
codec-http [maven-release-plugin] prepare for next development iteration 2015-11-10 22:59:33 +01:00
codec-http2 Forking Twitter's hpack 2015-11-14 10:13:32 -08:00
codec-memcache [maven-release-plugin] prepare for next development iteration 2015-11-10 22:59:33 +01:00
codec-mqtt [maven-release-plugin] prepare for next development iteration 2015-11-10 22:59:33 +01:00
codec-socks [maven-release-plugin] prepare for next development iteration 2015-11-10 22:59:33 +01:00
codec-stomp [maven-release-plugin] prepare for next development iteration 2015-11-10 22:59:33 +01:00
codec-xml [maven-release-plugin] prepare for next development iteration 2015-11-10 22:59:33 +01:00
common [maven-release-plugin] prepare for next development iteration 2015-11-10 22:59:33 +01:00
example [maven-release-plugin] prepare for next development iteration 2015-11-10 22:59:33 +01:00
handler [maven-release-plugin] prepare for next development iteration 2015-11-10 22:59:33 +01:00
handler-proxy [maven-release-plugin] prepare for next development iteration 2015-11-10 22:59:33 +01:00
license Forking Twitter's hpack 2015-11-14 10:13:32 -08:00
microbench Forking Twitter's hpack 2015-11-14 10:13:32 -08:00
resolver [maven-release-plugin] prepare for next development iteration 2015-11-10 22:59:33 +01:00
resolver-dns [maven-release-plugin] prepare for next development iteration 2015-11-10 22:59:33 +01:00
tarball [maven-release-plugin] prepare for next development iteration 2015-11-10 22:59:33 +01:00
testsuite [maven-release-plugin] prepare for next development iteration 2015-11-10 22:59:33 +01:00
testsuite-osgi [maven-release-plugin] prepare for next development iteration 2015-11-10 22:59:33 +01:00
transport [maven-release-plugin] prepare for next development iteration 2015-11-10 22:59:33 +01:00
transport-native-epoll [maven-release-plugin] prepare for next development iteration 2015-11-10 22:59:33 +01:00
transport-rxtx [maven-release-plugin] prepare for next development iteration 2015-11-10 22:59:33 +01:00
transport-sctp [maven-release-plugin] prepare for next development iteration 2015-11-10 22:59:33 +01:00
transport-udt [maven-release-plugin] prepare for next development iteration 2015-11-10 22:59:33 +01: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:36:54 +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:13: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:13:32 -08:00
pom.xml Forking Twitter's hpack 2015-11-14 10:13:32 -08:00
README.md Fix the 'branches to look' section 2015-10-27 13:59:11 +01:00
run-example.sh Add HTTP/2 Netty tiles example 2015-05-18 14:16:54 -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.