andreacavalli/netty5
1
0
Fork 0
Code Issues Pull Requests Projects Releases Wiki Activity
5,836 Commits 27 Branches 234 Tags 84 MiB
Java 99.8%
Shell 0.1%
ca7c53d45f
Go to file
nmittler ca7c53d45f Add support for HTTP/2 draft 12. 
Motivation:

Draft 12 has just arrived and has quite a few changes. Need to update in
order to keep current with the spec.

Modifications:

This is a rewrite of the original (draft 10) code. There are only 2
handlers now: preface and connection. The connection handler is now
callback based rather than frame based (there are no frame classes
anymore). AbstractHttp2ConnectionHandler is the base class for any
HTTP/2 handlers. All of the stream priority logic now resides in the
outbound flow controller, and its interface exposes methods for
adding/updating priority for streams.

Upgraded to hpack 0.7.0, which is used by draft12. Also removed
draft10 code and moved draft12 code to the ../http2 package
(no draft subpackage).

Result:

Addition of a HTTP/2 draft 12 support.
2014-05-06 20:22:27 +02:00
all Generate the default JAR to make oss.sonatype.org happy 2014-05-03 17:28:28 +09:00
buffer Synchronized between 4.1 and master 2014-04-25 00:36:01 +09:00
codec Fix chunk type for stream identifier 2014-04-19 21:06:46 +02:00
codec-http Adding short-curcuit option for CORS 2014-05-06 12:06:34 +02:00
codec-http2 Add support for HTTP/2 draft 12. 2014-05-06 20:22:27 +02:00
codec-memcache Synchronized between 4.1 and master 2014-04-25 00:36:01 +09:00
codec-socks Correctly handle SocksCmdResponse. Related to #2428 2014-04-30 10:45:14 +02:00
common Simplify native library resolution using os-maven-plugin 2014-05-02 04:21:29 +09:00
example Add support for HTTP/2 draft 12. 2014-05-06 20:22:27 +02:00
handler Correctly write pending data after ssl handshake completes. Related to [#2437] 2014-04-30 14:23:34 +02:00
license [#1259] Add optimized queue for SCMP pattern and use it in NIO and native transport 2014-02-27 13:56:15 +01:00
microbench Upgrade JMH to 0.4.1 and make use of @Params. 2014-02-23 16:39:15 +01:00
tarball [maven-release-plugin] prepare for next development iteration 2013-12-22 22:06:15 +09:00
testsuite Fix compile error 2014-04-30 15:58:33 +02:00
transport [#2454] Correctly return null when DefaultChannelPipeline.firstContext() is called on empty pipeline 2014-05-04 21:13:56 +02:00
transport-native-epoll Generate the default JAR to make oss.sonatype.org happy 2014-05-03 17:28:28 +09:00
transport-rxtx Resurrect channel deregistration and constructor changes 2014-04-24 20:54:50 +09:00
transport-sctp Synchronized between 4.1 and master again (part 2) 2014-04-25 15:07:12 +09:00
transport-udt Synchronized between 4.1 and master again (part 2) 2014-04-25 15:07:12 +09:00
.fbfilter.xml Update license headers 2012-06-04 13:31:44 -07:00
.fbprefs Updated Find Bugs configuration 2009-03-04 10:33:09 +00:00
.gitignore Format and partially describe Gitignore 2013-12-10 07:03:43 +01: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 [#1259] Add optimized queue for SCMP pattern and use it in NIO and native transport 2014-02-27 13:56:15 +01:00
pom.xml Generate the default JAR to make oss.sonatype.org happy 2014-05-03 17:28:28 +09:00
README.md Synchronized between 4.1 and master (part 3) 2014-04-25 16:17:16 +09:00

README.md

Netty Project

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

Links

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.