andreacavalli/netty5
1
0
Fork 0
Code Issues Pull Requests Projects Releases Wiki Activity
6,227 Commits 27 Branches 234 Tags 84 MiB
Java 99.8%
Shell 0.1%
338b60821d
Go to file
Trustin Lee 338b60821d Do not write LastHttpContent twice in HttpStaticFileServer example 
Related: #3122

Motivation:

The HttpStaticFileServer example writes the LastHttpContent twice at the
end of the transfer.  HttpChunkedInput already produces a
LastHttpContent at the end of the stream, so there's no reason to write
another.

Modifications:

Do not write LastHttpContent in HttpStaticFileServerHandler when
HttpChunkedInput is used to transfer a file.

Result:

HttpStaticFileServer does not violates the protocol anymore.
2014-11-21 11:43:32 +09:00
all Fix missing version properties of transport-epoll in all-in-one JAR 2014-10-21 22:36:10 +09:00
buffer Small performance improvements 2014-11-20 00:10:06 -05:00
codec Small performance improvements 2014-11-20 00:10:06 -05:00
codec-dns Add EDNS support to DnsQueryEncoder 2014-10-16 17:05:08 +09:00
codec-haproxy [maven-release-plugin] prepare for next development iteration 2014-08-16 03:27:42 +09:00
codec-http Add HttpStatusClass 2014-11-21 10:52:28 +09:00
codec-memcache Add proxy support for client socket connections 2014-10-14 12:29:08 +09:00
codec-mqtt Small performance improvements 2014-11-20 00:10:06 -05:00
codec-socks Add proxy support for client socket connections 2014-10-14 12:29:08 +09:00
codec-stomp Backport header improvements from 5.0 2014-11-01 00:59:57 +09:00
common Backport the IntObjectHashMap changes in f23f3b9617 2014-11-21 11:07:24 +09:00
example Do not write LastHttpContent twice in HttpStaticFileServer example 2014-11-21 11:43:32 +09:00
handler Small performance improvements 2014-11-20 00:10:06 -05:00
handler-proxy Use Proxy-Authorization instead of Authorization for proxy authentication 2014-11-20 20:41:09 +09:00
license Implemented LZMA frame encoder 2014-09-15 15:05:36 +02:00
microbench Benchmark for HttpRequestDecoder 2014-11-12 14:29:15 +01:00
resolver Name resolver API and DNS-based name resolver 2014-10-16 17:05:20 +09:00
resolver-dns Improve DnsNameResolverTest.testResolveA() 2014-10-25 17:29:06 +09:00
tarball [maven-release-plugin] prepare for next development iteration 2014-08-16 03:27:42 +09:00
testsuite Fix backward compatibility from the previous backport 2014-11-01 01:00:25 +09:00
transport Small performance improvements 2014-11-20 00:10:06 -05:00
transport-native-epoll Name resolver API and DNS-based name resolver 2014-10-16 17:05:20 +09:00
transport-rxtx [maven-release-plugin] prepare for next development iteration 2014-08-16 03:27:42 +09:00
transport-sctp [maven-release-plugin] prepare for next development iteration 2014-08-16 03:27:42 +09:00
transport-udt Small performance improvements 2014-11-20 00:10:06 -05: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 Implemented LZMA frame encoder 2014-09-15 15:05:36 +02:00
pom.xml Backport ALPN and Mutual Auth SSL 2014-10-31 12:52:26 +09:00
README.md Add a link to the 'native transports' page 2014-07-21 12:54:24 -07:00
run-example.sh Add logLevel property to enable different log levels for the examples. 2014-11-21 10:48:57 +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.