andreacavalli/netty5
1
0
Fork 0
Code Issues Pull Requests Projects Releases Wiki Activity
7,373 Commits 27 Branches 234 Tags 84 MiB
Java 99.8%
Shell 0.1%
da46928950
Go to file
Trustin Lee da46928950 Fix NPE when creating DomainNameMapping via a builder
2016-05-18 19:26:28 +09:00
all [maven-release-plugin] prepare for next development iteration 2016-04-10 08:37:18 +02:00
buffer Make retained derived buffers recyclable 2016-05-17 11:16:13 +02:00
codec Make retained derived buffers recyclable 2016-05-17 11:16:13 +02:00
codec-dns Make retained derived buffers recyclable 2016-05-17 11:16:13 +02:00
codec-haproxy [maven-release-plugin] prepare for next development iteration 2016-04-10 08:37:18 +02:00
codec-http HTTP/2 HPACK Header Name Validation and Trailing Padding 2016-05-17 13:42:16 -07:00
codec-http2 HTTP/2 HPACK Header Name Validation and Trailing Padding 2016-05-17 13:42:16 -07:00
codec-memcache Make retained derived buffers recyclable 2016-05-17 11:16:13 +02:00
codec-mqtt Make retained derived buffers recyclable 2016-05-17 11:16:13 +02:00
codec-redis Make retained derived buffers recyclable 2016-05-17 11:16:13 +02:00
codec-smtp Make retained derived buffers recyclable 2016-05-17 11:16:13 +02:00
codec-socks Make retained derived buffers recyclable 2016-05-17 11:16:13 +02:00
codec-stomp Make retained derived buffers recyclable 2016-05-17 11:16:13 +02:00
codec-xml Update dependencies 2016-04-14 11:05:53 +02:00
common Fix NPE when creating DomainNameMapping via a builder 2016-05-18 19:26:28 +09:00
example Make retained derived buffers recyclable 2016-05-17 11:16:13 +02:00
handler Replace DomainMappingBuilder with DomainNameMappingBuilder 2016-05-18 12:03:14 +02:00
handler-proxy [maven-release-plugin] prepare for next development iteration 2016-04-10 08:37:18 +02:00
license added support for Protobuf codec nano runtime 2016-01-19 21:39:17 +01:00
microbench Remove ChannelHandlerInvoker 2016-05-17 11:14:00 +02:00
resolver Change hosts file resolver to be case-insensitive 2016-05-10 08:57:48 +02:00
resolver-dns Do not send duplicate DNS queries when the same query is in progress already 2016-05-17 15:07:36 +02:00
tarball [maven-release-plugin] prepare for next development iteration 2016-04-10 08:37:18 +02:00
testsuite Make retained derived buffers recyclable 2016-05-17 11:16:13 +02:00
testsuite-osgi [maven-release-plugin] prepare for next development iteration 2016-04-10 08:37:18 +02:00
transport DuplexChannel to support shutdownInput 2016-05-18 09:11:49 +02:00
transport-native-epoll DuplexChannel to support shutdownInput 2016-05-18 09:11:49 +02:00
transport-rxtx DuplexChannel to support shutdownInput 2016-05-18 09:11:49 +02:00
transport-sctp Make retained derived buffers recyclable 2016-05-17 11:16:13 +02:00
transport-udt DuplexChannel to support shutdownInput 2016-05-18 09:11:49 +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 added support for Protobuf codec nano runtime 2016-01-19 21:39:17 +01:00
pom.xml Upgrade to netty-tcnative-1.1.33.Fork16 2016-05-13 08:40:37 +02:00
README.md Updating Branches to look section to match the current branching structure of the project 2016-03-10 22:08:01 +01:00
run-example.sh Add an example client for codec-redis 2016-04-23 11:18:12 -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

Development of all 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.