andreacavalli/netty5
1
0
Fork 0
Code Issues Pull Requests Projects Releases Wiki Activity
4,464 Commits 27 Branches 234 Tags 84 MiB
Java 99.8%
Shell 0.1%
b4bf565ad9
Go to file
Trustin Lee b4bf565ad9 Travis CI configuration
2013-03-11 08:47:12 +09:00
all [maven-release-plugin] prepare for next development iteration 2013-02-26 16:55:07 -08:00
buffer Javadocs cleanup / added 2013-03-10 21:07:19 +01:00
codec [#1131] Codecs must not cache next buffer during processing 2013-03-08 15:38:17 +01:00
codec-http Allow to specify the used buffer type for ChannelInboundByteBufHandler and ChannelOutboundByteBufHandler by configuration. As default it tries to use a direct ByteBuf 2013-03-08 08:20:46 +01:00
codec-socks [maven-release-plugin] prepare for next development iteration 2013-02-26 16:55:07 -08:00
common Fix a bug where TypeParameterMatcher raises ClassCastException when an instance with raw type parameter is given 2013-03-09 09:19:34 +09:00
example Allow to specify the used buffer type for ChannelInboundByteBufHandler and ChannelOutboundByteBufHandler by configuration. As default it tries to use a direct ByteBuf 2013-03-08 08:20:46 +01:00
handler Allow to specify the used buffer type for ChannelInboundByteBufHandler and ChannelOutboundByteBufHandler by configuration. As default it tries to use a direct ByteBuf 2013-03-08 08:20:46 +01:00
license Add back jzlib license file and notice 2013-02-21 14:00:59 -08:00
microbench Change ByteBufAllocator.buffer() to allocate a direct buffer only when the platform can handle a direct buffer reliably 2013-03-05 17:55:24 +09:00
tarball [maven-release-plugin] prepare for next development iteration 2013-02-26 16:55:07 -08:00
testsuite Allow to specify the used buffer type for ChannelInboundByteBufHandler and ChannelOutboundByteBufHandler by configuration. As default it tries to use a direct ByteBuf 2013-03-08 08:20:46 +01:00
testsuite-osgi [maven-release-plugin] prepare for next development iteration 2013-02-26 16:55:07 -08:00
transport Javadocs cleanup / added 2013-03-10 21:07:19 +01:00
transport-rxtx Allow to specify the used buffer type for ChannelInboundByteBufHandler and ChannelOutboundByteBufHandler by configuration. As default it tries to use a direct ByteBuf 2013-03-08 08:20:46 +01:00
transport-sctp Allow to specify the used buffer type for ChannelInboundByteBufHandler and ChannelOutboundByteBufHandler by configuration. As default it tries to use a direct ByteBuf 2013-03-08 08:20:46 +01:00
transport-udt Allow to specify the used buffer type for ChannelInboundByteBufHandler and ChannelOutboundByteBufHandler by configuration. As default it tries to use a direct ByteBuf 2013-03-08 08:20:46 +01:00
.fbfilter.xml Update license headers 2012-06-04 13:31:44 -07:00
.fbprefs Updated Find Bugs configuration 2009-03-04 10:33:09 +00:00
.gitignore ignore .idea/ folder 2012-01-16 16:01:00 +08:00
.travis.yml Travis CI configuration 2013-03-11 08:47:12 +09:00
LICENSE.txt Relicensed to Apache License v2 2009-08-28 07:15:49 +00:00
NOTICE.txt Add back jzlib license file and notice 2013-02-21 14:00:59 -08:00
pom.xml [maven-release-plugin] prepare for next development iteration 2013-02-26 16:55:07 -08:00
README.md Fix broken url 2013-02-26 16:29:24 -08: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