Go to file
Scott Mitchell c7e3f6c6fd HTTP/2 defines using String instead of CharSequence
Motivation:
Http2CodecUtils has some static variables which are defined as Strings instead of CharSequence. One of these defines is used as a header name and should be AsciiString.

Modifications:
- Change the String defines in Http2CodecUtils to CharSequence

Result:
Types are more consistently using CharSequence and adding the upgrade header will require less work.
2015-09-16 14:55:33 -07:00
all [maven-release-plugin] prepare for next development iteration 2015-09-02 11:45:20 +02:00
buffer Optimize ByteBufUtil.writeUsAscii(...) when AsciiString is used. 2015-09-15 12:26:58 +02:00
codec HTTP/2 Header Name Validation 2015-09-09 13:59:08 -07:00
codec-dns [maven-release-plugin] prepare for next development iteration 2015-09-02 11:45:20 +02:00
codec-haproxy [maven-release-plugin] prepare for next development iteration 2015-09-02 11:45:20 +02:00
codec-http HTTP/2 defines using String instead of CharSequence 2015-09-16 14:55:33 -07:00
codec-http2 HTTP/2 defines using String instead of CharSequence 2015-09-16 14:55:33 -07:00
codec-memcache [maven-release-plugin] prepare for next development iteration 2015-09-02 11:45:20 +02:00
codec-mqtt [maven-release-plugin] prepare for next development iteration 2015-09-02 11:45:20 +02:00
codec-socks [maven-release-plugin] prepare for next development iteration 2015-09-02 11:45:20 +02:00
codec-stomp [maven-release-plugin] prepare for next development iteration 2015-09-02 11:45:20 +02:00
codec-xml [maven-release-plugin] prepare for next development iteration 2015-09-02 11:45:20 +02:00
common HTTP/2 defines using String instead of CharSequence 2015-09-16 14:55:33 -07:00
example HTTP/2 defines using String instead of CharSequence 2015-09-16 14:55:33 -07:00
handler Support SSLSession.getLocalCertificates() and getLocalPrincipal() when using OpenSSL 2015-09-15 12:22:00 +02:00
handler-proxy [maven-release-plugin] prepare for next development iteration 2015-09-02 11:45:20 +02:00
license Let PoolThreadCache work even if allocation and deallocation Thread are different 2015-05-27 14:38:11 +02:00
microbench [maven-release-plugin] prepare for next development iteration 2015-09-02 11:45:20 +02:00
resolver [maven-release-plugin] prepare for next development iteration 2015-09-02 11:45:20 +02:00
resolver-dns [maven-release-plugin] prepare for next development iteration 2015-09-02 11:45:20 +02:00
tarball [maven-release-plugin] prepare for next development iteration 2015-09-02 11:45:20 +02:00
testsuite Correctly throw SSLPeerUnverifiedException if peers identity has not been verified 2015-09-15 09:57:45 +02:00
testsuite-osgi [maven-release-plugin] prepare for next development iteration 2015-09-02 11:45:20 +02:00
transport Ensure close caused by write will happen before write promise is notified 2015-09-16 20:36:04 +02:00
transport-native-epoll [#4205] Correctly set EPOLLOUT flag whe writeBytes(...) was not able to write everything 2015-09-16 07:30:17 +02:00
transport-rxtx [maven-release-plugin] prepare for next development iteration 2015-09-02 11:45:20 +02:00
transport-sctp [maven-release-plugin] prepare for next development iteration 2015-09-02 11:45:20 +02:00
transport-udt [maven-release-plugin] prepare for next development iteration 2015-09-02 11:45:20 +02: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 Let PoolThreadCache work even if allocation and deallocation Thread are different 2015-05-27 14:38:11 +02:00
pom.xml Update twitter hpack version 2015-09-14 13:16:36 -07:00
README.md Add a link to the 'native transports' page 2014-07-21 12:54:24 -07: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.