Go to file
Lionel Li e069079aff Adapt Http2ServerDowngrader to work with clients
Motivation:
Http2ServerDowngrader is specifically built for server channels where
inbound Http2StreamFrames are converted into HttpRequests, and outbound
HttpResponses are converted into Http2StreamFrames. It can be easily
made to be more generic to work with client channels where inbound
Http2StreamFrames are converted into HttpResponses, and outbound
HttpRequests are converted into Http2StreamFrames.

Modification:
- Renamed Http2ServerDowngrader to a more general
  Http2StreamFrameToHttpObjectCodec
- Made it take in an "isServer" parameter to determine whether encoding
  inbound Http2StreamFrames should create HttpRequests (for server) or
  HttpResponses (for client)
- Norman fixed a leak in the unit test. Thanks! :-)

Result:
Now Http2StreamFrameToHttpObjectCodec can be used to translate
Http2StreamFrame to HttpObject for both server and client.
2017-09-22 11:04:43 -07:00
.github Use GitHub Issue/PR Template Feature 2016-12-07 11:40:26 -08:00
all Correctly filter out native tcnative lib 2017-09-18 11:43:17 -07:00
bom [maven-release-plugin] prepare for next development iteration 2017-08-24 15:38:22 +02:00
buffer Expose all defaults on PooledByteBufAllocator 2017-09-20 21:48:53 -07:00
codec Use offset finding eol avoid repeated scaning. 2017-09-17 09:17:38 -07:00
codec-dns [maven-release-plugin] prepare for next development iteration 2017-08-24 15:38:22 +02:00
codec-haproxy [maven-release-plugin] prepare for next development iteration 2017-08-24 15:38:22 +02:00
codec-http Correctly not write any body when 1xx, 204 or 304 is used as response status code. 2017-09-20 07:41:13 -07:00
codec-http2 Adapt Http2ServerDowngrader to work with clients 2017-09-22 11:04:43 -07:00
codec-memcache [maven-release-plugin] prepare for next development iteration 2017-08-24 15:38:22 +02:00
codec-mqtt MQTT encode doesn't complain if password is set but username not 2017-09-14 09:37:37 -07:00
codec-redis [maven-release-plugin] prepare for next development iteration 2017-08-24 15:38:22 +02:00
codec-smtp [maven-release-plugin] prepare for next development iteration 2017-08-24 15:38:22 +02:00
codec-socks DefaultSocks5CommandRequest incorrectly rejects SOCKS5 commands with dstPort=0 2017-08-29 15:03:09 +02:00
codec-stomp Fix StompSubframeDecoder.readHeaders produce not any notification when parsed line that contains multiple colon 2017-08-29 22:06:45 +02:00
codec-xml [maven-release-plugin] prepare for next development iteration 2017-08-24 15:38:22 +02:00
common Fix regression in reporting leaks introduced by 3c8c7fc7e9. 2017-09-21 12:17:43 -07:00
dev-tools [maven-release-plugin] prepare for next development iteration 2017-08-24 15:38:22 +02:00
example [maven-release-plugin] prepare for next development iteration 2017-08-24 15:38:22 +02:00
handler Update SSLEngineTest certificate validity 2017-09-20 21:47:38 -07:00
handler-proxy [maven-release-plugin] prepare for next development iteration 2017-08-24 15:38:22 +02:00
license Remove reference to akka code and ArrayDeque which is not part of netty anymore 2017-03-07 21:30:51 +01:00
microbench Reduce performance overhead of ResourceLeakDetector 2017-09-18 16:36:19 -07:00
resolver [maven-release-plugin] prepare for next development iteration 2017-08-24 15:38:22 +02:00
resolver-dns [maven-release-plugin] prepare for next development iteration 2017-08-24 15:38:22 +02:00
tarball [maven-release-plugin] prepare for next development iteration 2017-08-24 15:38:22 +02:00
testsuite Fix assertion error when closing / shutdown native channel and SO_LINGER is set. 2017-09-18 14:46:37 -07:00
testsuite-autobahn [maven-release-plugin] prepare for next development iteration 2017-08-24 15:38:22 +02:00
testsuite-osgi [maven-release-plugin] prepare for next development iteration 2017-08-24 15:38:22 +02:00
transport Fix assertion error when closing / shutdown native channel and SO_LINGER is set. 2017-09-18 14:46:37 -07:00
transport-native-epoll Check for latest centos release version when doing a release 2017-09-21 12:23:37 -07:00
transport-native-kqueue Fix assertion error when closing / shutdown native channel and SO_LINGER is set. 2017-09-18 14:46:37 -07:00
transport-native-unix-common [maven-release-plugin] prepare for next development iteration 2017-08-24 15:38:22 +02:00
transport-native-unix-common-tests [maven-release-plugin] prepare for next development iteration 2017-08-24 15:38:22 +02:00
transport-rxtx Remove @Deprecated from package-info.java as intellij not likes it 2017-09-18 13:44:22 -07:00
transport-sctp [maven-release-plugin] prepare for next development iteration 2017-08-24 15:38:22 +02:00
transport-udt [maven-release-plugin] prepare for next development iteration 2017-08-24 15:38:22 +02:00
.fbprefs Updated Find Bugs configuration 2009-03-04 10:33:09 +00:00
.gitignore Use shaded dependency on JCTools instead of copy and paste 2016-06-10 13:19:45 +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:13:58 +09:00
LICENSE.txt Relicensed to Apache License v2 2009-08-28 07:15:49 +00:00
NOTICE.txt Remove reference to akka code and ArrayDeque which is not part of netty anymore 2017-03-07 21:30:51 +01:00
pom.xml [maven-release-plugin] prepare for next development iteration 2017-08-24 15:38:22 +02:00
README.md Updating Branches to look section to match the current branching structure of the project 2016-03-10 22:08:01 +01:00
run-example.sh Add UptimeServer and adjust UptimeClient's code style. 2017-04-28 07:41:07 +02: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

Development of all 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.