andreacavalli/netty5
1
0
Fork 0
Code Issues Pull Requests Projects Releases Wiki Activity
4,490 Commits 27 Branches 234 Tags 84 MiB
Java 99.8%
Shell 0.1%
42e31a4445
Go to file
Trustin Lee 42e31a4445 Revert "[#1131] Codecs must not cache next buffer during processing" 
This reverts commit b1775a3223.
2013-03-13 15:17:06 +09:00
all [maven-release-plugin] prepare for next development iteration 2013-02-26 16:55:07 -08:00
buffer Fix a memory leak in AbstractCompositeByteBufTest 2013-03-13 15:09:26 +09:00
codec Revert "[#1131] Codecs must not cache next buffer during processing" 2013-03-13 15:17:06 +09:00
codec-http Fix test failures 2013-03-12 14:43:38 +09:00
codec-socks [maven-release-plugin] prepare for next development iteration 2013-02-26 16:55:07 -08:00
common Revert e66fc219ff 2013-03-12 16:44:25 +09:00
example Upgrade to protobuf 2.5 and take advantage of MessageLite.getParserFromType() 2013-03-12 16:25:35 +09:00
handler Let ChannelGroupFuture extends ChannelFuture and ChannelGroupFutureListener GenericFutureListener 2013-03-12 08:35:39 +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 Make sure we handle outbound messages of type ByteBuf special 2013-03-11 08:59:00 +09:00
testsuite-osgi [maven-release-plugin] prepare for next development iteration 2013-02-26 16:55:07 -08:00
transport Fix issue where the bytes/messages are forwarded to the wrong handler 2013-03-12 08:37:27 +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 branch whitelisting 2013-03-11 09:55:43 +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 Upgrade to protobuf 2.5 and take advantage of MessageLite.getParserFromType() 2013-03-12 16:25:35 +09: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