andreacavalli/netty5
1
0
Fork 0
Code Issues Pull Requests Projects Releases Wiki Activity
6,871 Commits 27 Branches 234 Tags 84 MiB
Java 99.8%
Shell 0.1%
bd5091a14f
Go to file
Norman Maurer bd5091a14f Fix compilation failure introduced by f8019ba481
2015-08-21 09:37:24 +02:00
all [maven-release-plugin] prepare for next development iteration 2015-03-03 08:30:59 -05:00
buffer MemoryRegionCache$Entry objects are not recycled 2015-08-10 21:29:39 +02:00
codec HttpObjectAggregator doesn't check content-length header 2015-08-17 09:29:39 -07:00
codec-dns Provide more control over DnsNameResolver.query() / Add NameResolver.resolveAll() 2015-08-18 17:41:38 +09:00
codec-haproxy Add ProtocolDetectionResult and use it in HAProxyMessageDecoder for allow detect HAProxy protocol. 2015-06-23 08:59:16 +02:00
codec-http Fix compilation failure introduced by f8019ba481 2015-08-21 09:37:24 +02:00
codec-http2 HTTP/2 Graceful Shutdown Timeout 2015-08-20 13:24:23 -07:00
codec-memcache Remove Erroneous imports 2015-08-17 10:12:10 -07:00
codec-mqtt MqttEncoder build failure 2015-07-30 10:19:17 -07:00
codec-socks [maven-release-plugin] prepare for next development iteration 2015-03-03 08:30:59 -05:00
codec-stomp HttpObjectAggregator doesn't check content-length header 2015-08-17 09:29:39 -07:00
codec-xml [maven-release-plugin] prepare for next development iteration 2015-03-03 08:30:59 -05:00
common StringUtil not closing Formatter 2015-08-20 09:49:17 -07:00
example Headers Performance Boost and Interface Simplification 2015-08-12 15:54:44 -07:00
handler Consistent naming style for enum 2015-08-21 07:18:36 +02:00
handler-proxy ByteString introduced as AsciiString super class 2015-04-15 10:45:18 -07:00
license Let PoolThreadCache work even if allocation and deallocation Thread are different 2015-05-27 14:38:23 +02:00
microbench Headers Performance Boost and Interface Simplification 2015-08-12 15:54:44 -07:00
resolver Provide more control over DnsNameResolver.query() / Add NameResolver.resolveAll() 2015-08-18 17:41:38 +09:00
resolver-dns Add a test case for DNS resolver cache for negative loopups 2015-08-18 18:45:44 +09:00
tarball [maven-release-plugin] prepare for next development iteration 2015-03-03 08:30:59 -05:00
testsuite Allow to create SslContext from existing PrivateKey / X509Certificate 2015-08-12 15:19:18 +02:00
testsuite-osgi Add a property to disable osgi testsuite run 2015-08-13 09:52:46 +09:00
transport Provide more control over DnsNameResolver.query() / Add NameResolver.resolveAll() 2015-08-18 17:41:38 +09:00
transport-native-epoll EPOLL exception processing feedback loop 2015-08-20 13:11:21 -07:00
transport-rxtx maxBytesPerRead channel configuration 2015-08-06 00:00:28 -07:00
transport-sctp a48e5c7347 merge build failure 2015-08-06 10:28:39 -07:00
transport-udt a48e5c7347 merge build failure 2015-08-06 10:28:39 -07:00
.fbprefs Updated Find Bugs configuration 2009-03-04 10:33:09 +00:00
.gitignore Exclude bin directory from git Motivation: 2014-08-27 06:33:22 +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:17: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:23 +02:00
pom.xml Correct OSGi manifests in source jars 2015-08-21 12:57:40 +09:00
README.md Add a link to the 'native transports' page 2014-07-21 12:10:16 -07:00
run-example.sh Add HTTP/2 Netty tiles example 2015-05-18 14:17:48 -07: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.