andreacavalli/netty5
1
0
Fork 0
Code Issues Pull Requests Projects Releases Wiki Activity
6,785 Commits 27 Branches 234 Tags 84 MiB
Java 99.8%
Shell 0.1%
acf1b0f90b
Go to file
James Lee acf1b0f90b Fix code styles on MQTT codec classes
2015-08-31 08:25:36 +02:00
all [maven-release-plugin] prepare for next development iteration 2015-05-07 14:21:08 -04:00
buffer Additional configuration for leak detection 2015-08-30 20:50:10 +02:00
codec [#4087] Correctly forward bytes when remove codec and handle channelInactive / channelReadComplete(...) 2015-08-21 18:26:32 +02:00
codec-dns Provide more control over DnsNameResolver.query() / Add NameResolver.resolveAll() 2015-08-18 17:40:13 +09:00
codec-haproxy Add ProtocolDetectionResult and use it in HAProxyMessageDecoder for allow detect HAProxy protocol. 2015-06-23 08:59:07 +02:00
codec-http [#2677] Remove unnessary synchronized in SpdySessionHandler 2015-08-28 23:14:13 +02:00
codec-http2 DefaultPropertyKey private member variable accessed outside scope 2015-08-28 08:54:11 -07:00
codec-memcache Fix a buffer leak in BinaryMemcacheEncoderTest 2015-08-29 11:54:01 +09:00
codec-mqtt Fix code styles on MQTT codec classes 2015-08-31 08:25:36 +02:00
codec-socks [maven-release-plugin] prepare for next development iteration 2015-05-07 14:21:08 -04:00
codec-stomp HttpObjectAggregator doesn't check content-length header 2015-08-17 09:26:50 -07:00
codec-xml [maven-release-plugin] prepare for next development iteration 2015-05-07 14:21:08 -04:00
common Additional configuration for leak detection 2015-08-30 20:50:10 +02:00
example Refactor of HttpUtil and HttpHeaderUtil 2015-08-27 08:49:58 -07:00
handler Revert "Consistent naming style for enum" 2015-08-28 20:49:38 +02:00
handler-proxy [maven-release-plugin] prepare for next development iteration 2015-05-07 14:21:08 -04:00
license Let PoolThreadCache work even if allocation and deallocation Thread are different 2015-05-27 14:38:11 +02:00
microbench Headers Performance Boost and Interface Simplification 2015-08-17 08:50:11 -07:00
resolver Provide more control over DnsNameResolver.query() / Add NameResolver.resolveAll() 2015-08-18 17:40:13 +09:00
resolver-dns Fix unintended timeout in negative DNS lookup cache test 2015-08-29 11:40:32 +09:00
tarball [maven-release-plugin] prepare for next development iteration 2015-05-07 14:21:08 -04:00
testsuite Refactor of HttpUtil and HttpHeaderUtil 2015-08-27 08:49:58 -07:00
testsuite-osgi Add a property to disable osgi testsuite run 2015-08-13 09:53:26 +09:00
transport LocalChannelWrite event sequencing issue 2015-08-28 11:26:59 -07:00
transport-native-epoll Use ChannelException when ChannelConfig operation fails in epoll. 2015-08-28 21:38:35 +02:00
transport-rxtx maxBytesPerRead channel configuration 2015-08-05 23:59:54 -07:00
transport-sctp OioSctpChannel iterating over selected keys 2015-08-27 10:22:36 -07:00
transport-udt maxBytesPerRead channel configuration 2015-08-05 23:59:54 -07: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 Let PoolThreadCache work even if allocation and deallocation Thread are different 2015-05-27 14:38:11 +02:00
pom.xml Build fails with java 1.8_u60 2015-08-28 08:56:28 -07:00
README.md Add a link to the 'native transports' page 2014-07-21 12:54:24 -07:00
run-example.sh Add HTTP/2 Netty tiles example 2015-05-18 14:16:54 -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.