andreacavalli/netty5
1
0
Fork 0
Code Issues Pull Requests Projects Releases Wiki Activity
6,669 Commits 27 Branches 234 Tags 84 MiB
Java 99.8%
Shell 0.1%
410aa427be
Go to file
Trustin Lee 410aa427be Fix a test failure in DnsQueryTest
2015-05-01 12:04:05 +09:00
all [maven-release-plugin] prepare for next development iteration 2015-03-03 08:30:59 -05:00
buffer ByteString arrayOffset method 2015-04-24 18:54:19 -07:00
codec Remove memory copy when extract frame in LengthFieldBasedFrameDecoder 2015-04-29 08:43:21 +02:00
codec-dns Fix a test failure in DnsQueryTest 2015-05-01 12:04:05 +09:00
codec-haproxy ByteString introduced as AsciiString super class 2015-04-15 10:45:18 -07:00
codec-http ByteString arrayOffset master branch cleanup 2015-04-25 14:24:39 -07:00
codec-http2 Remove explicit flushes from HTTP2 encoders, decoders & flow-controllers 2015-04-30 17:44:53 -07:00
codec-memcache Returns after encoding each message not do check following instance types 2015-03-19 20:43:10 +01:00
codec-mqtt [maven-release-plugin] prepare for next development iteration 2015-03-03 08:30:59 -05:00
codec-socks [maven-release-plugin] prepare for next development iteration 2015-03-03 08:30:59 -05:00
codec-stomp ByteString introduced as AsciiString super class 2015-04-15 10:45:18 -07:00
codec-xml [maven-release-plugin] prepare for next development iteration 2015-03-03 08:30:59 -05:00
common Revamp DNS codec 2015-05-01 11:34:52 +09:00
example ByteString introduced as AsciiString super class 2015-04-15 10:45:18 -07:00
handler Fix SslContextBuilder swapping client and server 2015-04-20 17:25:39 -07:00
handler-proxy ByteString introduced as AsciiString super class 2015-04-15 10:45:18 -07:00
license Integrate non-blocking XML parser as Netty codec (#2806) 2015-02-19 14:17:17 +01:00
microbench ByteString arrayOffset method 2015-04-24 18:54:19 -07:00
resolver Use InetSocketAddress.getHostName() instead of getHostString() 2015-03-10 11:45:56 +09:00
resolver-dns Revamp DNS codec 2015-05-01 11:34:52 +09:00
tarball [maven-release-plugin] prepare for next development iteration 2015-03-03 08:30:59 -05:00
testsuite Reduce the memory requirement of heap dump compression 2015-05-01 11:55:06 +09:00
testsuite-osgi Upgrade twitter hpack dependency 2015-04-30 17:14:33 -07:00
transport Revamp DNS codec 2015-05-01 11:34:52 +09:00
transport-native-epoll Add support for splice(...) 2015-04-30 07:29:21 +02:00
transport-rxtx [maven-release-plugin] prepare for next development iteration 2015-03-03 08:30:59 -05:00
transport-sctp Add support for SCTP 'unordered' flag. 2015-04-30 08:46:34 +02:00
transport-udt Motivation: If there are no readable bytes, it's unnecessary to go through javaChannel().write(). 2015-04-08 09:35:33 +02: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 Integrate non-blocking XML parser as Netty codec (#2806) 2015-02-19 14:17:17 +01:00
pom.xml Upgrade twitter hpack dependency 2015-04-30 17:14:33 -07:00
README.md Add a link to the 'native transports' page 2014-07-21 12:10:16 -07:00
run-example.sh Add logLevel property to enable different log levels for the examples. 2014-11-21 10:49:27 +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.