andreacavalli/netty5
1
0
Fork 0
Code Issues Pull Requests Projects Releases Wiki Activity
6,504 Commits 27 Branches 234 Tags 84 MiB
Java 99.8%
Shell 0.1%
e48e6e4509
Go to file
Trustin Lee e48e6e4509 Fix checkstyle
2015-04-17 11:39:36 +09:00
all HTTP/2 codec missing from all/pom.xml 2015-03-23 16:29:28 -07:00
buffer ByteString introduced as AsciiString super class 2015-04-14 16:35:17 -07:00
codec ByteString introduced as AsciiString super class 2015-04-14 16:35:17 -07:00
codec-dns [maven-release-plugin] prepare for next development iteration 2015-03-03 02:06:47 -05:00
codec-haproxy ByteString introduced as AsciiString super class 2015-04-14 16:35:17 -07:00
codec-http Change AggregatedFullHttpMessage to contain a content ByteBuf 2015-04-16 14:43:50 +02:00
codec-http2 HTTP/2 Priority tree circular link 2015-04-15 14:26:05 -07:00
codec-memcache Returns after encoding each message not do check following instance types 2015-03-19 20:43:59 +01:00
codec-mqtt [maven-release-plugin] prepare for next development iteration 2015-03-03 02:06:47 -05:00
codec-socks Hide password in exception messages of SocksAuthRequest 2015-03-17 17:25:09 +09:00
codec-stomp ByteString introduced as AsciiString super class 2015-04-14 16:35:17 -07:00
codec-xml [maven-release-plugin] prepare for next development iteration 2015-03-03 02:06:47 -05:00
common Fix checkstyle 2015-04-17 11:39:36 +09:00
example ByteString introduced as AsciiString super class 2015-04-14 16:35:17 -07:00
handler The "null" ClassLoader is the bootstrap ClassLoader 2015-04-16 17:26:09 +02:00
handler-proxy ByteString introduced as AsciiString super class 2015-04-14 16:35:17 -07:00
license Integrate non-blocking XML parser as Netty codec (#2806) 2015-02-19 13:46:14 +01:00
microbench Improve performance of AsciiString.equals(Object). 2015-04-16 17:29:54 -07:00
resolver Use InetSocketAddress.getHostName() instead of getHostString() 2015-03-10 11:49:23 +09:00
resolver-dns [maven-release-plugin] prepare for next development iteration 2015-03-03 02:06:47 -05:00
tarball [maven-release-plugin] prepare for next development iteration 2015-03-03 02:06:47 -05:00
testsuite [maven-release-plugin] prepare for next development iteration 2015-03-03 02:06:47 -05:00
testsuite-osgi [maven-release-plugin] prepare for next development iteration 2015-03-03 02:06:47 -05:00
transport Small typos fixes in Channel's Javadoc 2015-03-21 16:10:24 +01:00
transport-native-epoll [#3539] Correctly handle EPOLLRDHUP 2015-04-14 06:57:11 +02:00
transport-rxtx [maven-release-plugin] prepare for next development iteration 2015-03-03 02:06:47 -05:00
transport-sctp [maven-release-plugin] prepare for next development iteration 2015-03-03 02:06:47 -05:00
transport-udt Motivation: If there are no readable bytes, it's unnecessary to go through javaChannel().write(). 2015-04-08 09:36:24 +02: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 Integrate non-blocking XML parser as Netty codec (#2806) 2015-02-19 13:46:14 +01:00
pom.xml Add support for ALPN when using openssl + NPN client mode and support for CipherSuiteFilter 2015-04-10 18:52:34 +02:00
README.md Add a link to the 'native transports' page 2014-07-21 12:54:24 -07:00
run-example.sh HTTP/2 examples run script support 2015-03-23 16:27:55 -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.