3ebc1ab321
Motivation: I found myself writing AsciiString constants in my code for response statuses and thought that perhaps it might be nice to have them defined by Netty instead. Modifications: Adding codeAsText to HttpResponseStatus that returns the status code as AsciiText. In addition, added the 421 Misdirected Request response code from https://tools.ietf.org/html/draft-ietf-httpbis-http2-15#section-9.1.2 This response header was renamed in draft 15: https://tools.ietf.org/html/draft-ietf-httpbis-http2-15#appendix-A.1 But the code itself was not changed, and I thought using the latest would be better. Result: It is now possible to specify a status like this: new DefaultHttp2Headers().status(HttpResponseStatus.OK.codeAsText()); |
||
---|---|---|
all | ||
buffer | ||
codec | ||
codec-dns | ||
codec-haproxy | ||
codec-http | ||
codec-memcache | ||
codec-mqtt | ||
codec-socks | ||
codec-stomp | ||
common | ||
example | ||
handler | ||
handler-proxy | ||
license | ||
microbench | ||
resolver | ||
resolver-dns | ||
tarball | ||
testsuite | ||
transport | ||
transport-native-epoll | ||
transport-rxtx | ||
transport-sctp | ||
transport-udt | ||
.fbprefs | ||
.gitignore | ||
.travis.yml | ||
CONTRIBUTING.md | ||
LICENSE.txt | ||
NOTICE.txt | ||
pom.xml | ||
README.md | ||
run-example.sh |
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:
- Latest stable Oracle JDK 7
- Latest stable Apache Maven
- If you are on Linux, you need additional development packages installed on your system, because you'll build the native transport.
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.