andreacavalli/netty5
1
0
Fork 0
Code Issues Pull Requests Projects Releases Wiki Activity
6,719 Commits 27 Branches 234 Tags 84 MiB
Java 99.8%
Shell 0.1%
1645e97c2e
Go to file
Ruslan Sennov 1645e97c2e QueryStringDecoder's javadoc fix
2015-05-21 11:45:17 +02:00
all [maven-release-plugin] prepare for next development iteration 2015-03-03 08:30:59 -05:00
buffer Expose metrics for PooledByteBufAllocator 2015-05-20 21:06:48 +02:00
codec Remove memory copy when extract frame in LengthFieldBasedFrameDecoder 2015-04-29 08:43:21 +02:00
codec-dns Fix missing ResourceLeak.close() in AbstractDnsMessage 2015-05-04 12:07:59 +09:00
codec-haproxy ByteString introduced as AsciiString super class 2015-04-15 10:45:18 -07:00
codec-http QueryStringDecoder's javadoc fix 2015-05-21 11:45:17 +02:00
codec-http2 Fixing logging of ping acks in Http2OutboundFrameLogger 2015-05-20 08:58:48 -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 Expose metrics for PooledByteBufAllocator 2015-05-20 21:06:48 +02:00
example Fix merge error from f45d754 2015-05-18 14:23:56 -07:00
handler Do not call System.nanoTime() in ReadTimeoutHandler.channelRead() 2015-05-21 07:14:24 +02: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 Have Http2LocalFlowController.consumeBytes indicate whether a WINDOW_UPDATE was written 2015-05-04 13:21:53 -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 Fix compile error introduced by cherry-pick edf1eb10d5 2015-05-07 18:43:12 +02:00
testsuite-osgi Upgrade twitter hpack dependency 2015-04-30 17:14:33 -07:00
transport Scoring loopback addresses as 0 in DefaultChannelId 2015-05-08 13:14:10 -07:00
transport-native-epoll Fix regression introduced by 08e4b076be. 2015-05-06 17:57:24 +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 Remove duplicated code in AcceptorChannel classes. 2015-05-07 06:32:13 +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 [#3784] Support hostname verification when using OpenSSLEngine 2015-05-18 08:17:13 +02: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.