andreacavalli/netty5
1
0
Fork 0
Code Issues Pull Requests Projects Releases Wiki Activity
6,274 Commits 27 Branches 234 Tags 84 MiB
Java 99.8%
Shell 0.1%
4f7632a853
Go to file
Trustin Lee 4f7632a853 Fix checkstyle
2014-12-16 20:34:18 +09:00
all Fix missing version properties of transport-epoll in all-in-one JAR 2014-10-21 22:36:10 +09:00
buffer Ensure buffer is not released when call array() / memoryAddress() 2014-12-11 11:30:31 +01:00
codec Motivation: Sonar points out an equals comparison, where the types compared are different and don't share any common parent http://clinker.netty.io/sonar/drilldown/issues/io.netty:netty-parent:master?severity=CRITICAL# 2014-12-16 07:17:31 +01: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 Motivation: Sonar points out an equals comparison, where the types compared are different and don't share any common parent http://clinker.netty.io/sonar/drilldown/issues/io.netty:netty-parent:master?severity=CRITICAL# 2014-12-16 07:17:31 +01:00
codec-memcache Add proxy support for client socket connections 2014-10-14 12:29:08 +09:00
codec-mqtt Fix dependency issues with hamcrest 2014-12-04 17:59:15 +09:00
codec-socks Add proxy support for client socket connections 2014-10-14 12:29:08 +09:00
codec-stomp Headers set/add/contains timeMillis methods 2014-12-06 22:40:28 +09:00
common Fixing minor typo in FastThreadLocal javadoc. 2014-12-08 13:52:54 +01:00
example example: memcache: fix set command 2014-12-05 08:59:23 +01:00
handler Make sure to notify handshake success even if SSLEngine is closed 2014-12-12 11:55:27 +09: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 Fix Java 6 compatibility issue in DnsNameResolver 2014-12-06 22:31:44 +09:00
tarball [maven-release-plugin] prepare for next development iteration 2014-08-16 03:27:42 +09:00
testsuite Fix checkstyle 2014-12-16 20:34:18 +09:00
transport Fix documentation for ChannelHandlerContext#fireChannelReadComplete 2014-12-12 18:43:06 +01:00
transport-native-epoll Generate non-test JAR for netty-testsuite 2014-12-15 09:18:08 +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 Fix build errors due to missing dependency 2014-12-14 21:29:52 +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.