Go to file
Trustin Lee c25513d5e1 Upgrade to protobuf 2.5 and take advantage of MessageLite.getParserFromType()
- also fall back to MessageBuilder if getParserFromType() is not available.
2013-03-12 16:25:35 +09:00
all [maven-release-plugin] prepare for next development iteration 2013-02-26 16:55:07 -08:00
buffer Reschedule the streaming API for later 2013-03-12 13:08:10 +09:00
codec Upgrade to protobuf 2.5 and take advantage of MessageLite.getParserFromType() 2013-03-12 16:25:35 +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 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 Upgrade to protobuf 2.5 and take advantage of MessageLite.getParserFromType() 2013-03-12 16:25:35 +09:00
handler Make sure we handle outbound messages of type ByteBuf special 2013-03-11 08:59:00 +09: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 Allow SingleOutboundMessageHandler.beginFlush() to reject the flush request by returning false / Replace PartialFlushException with IncompleteFlushException which is more correct. 2013-03-12 15:20:46 +09: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

Netty Project

Netty is an asynchronous event-driven network application framework for rapid development of maintainable high performance protocol servers & clients.

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