Go to file
Norman Maurer 12a3e23e47 MessageToByteEncoder always starts with ByteBuf that use initalCapacity == 0
Motivation:

MessageToByteEncoder always starts with ByteBuf that use initalCapacity == 0 when preferDirect is used. This is really wasteful in terms of performance as every first write into the buffer will cause an expand of the buffer itself.

Modifications:

 - Change ByteBufAllocator.ioBuffer() use the same default initialCapacity as heapBuffer() and directBuffer()
 - Add new allocateBuffer method to MessageToByteEncoder that allow the user to do some smarter allocation based on the message that will be encoded.

Result:

Less expanding of buffer and more flexibilty when allocate the buffer for encoding.
2014-06-24 13:55:21 +09:00
all Add MQTT protocol codec 2014-06-21 16:52:10 +09:00
buffer MessageToByteEncoder always starts with ByteBuf that use initalCapacity == 0 2014-06-24 13:55:21 +09:00
codec MessageToByteEncoder always starts with ByteBuf that use initalCapacity == 0 2014-06-24 13:55:21 +09:00
codec-dns DNS codec for Netty which is based on the work of [#1622]. 2014-06-10 09:57:06 +02:00
codec-haproxy Fix test failures due to incorrect validation 2014-06-21 17:11:35 +09:00
codec-http Refactor FastThreadLocal to simplify TLV management 2014-06-19 21:13:55 +09:00
codec-memcache Introduce MessageAggregator and DecoderResultProvider 2014-06-05 16:51:14 +09:00
codec-mqtt Mqtt -> MQTT 2014-06-21 17:14:41 +09:00
codec-socks Clean up the examples 2014-05-23 17:13:09 +09:00
codec-stomp Introduce TextHeaders and AsciiString 2014-06-14 15:36:19 +09:00
common Remove padding utility classes 2014-06-21 17:59:49 +09:00
example Make use of HttpChunkedInput as this will also work when compression is used 2014-06-23 09:38:48 +02:00
handler Refactor FastThreadLocal to simplify TLV management 2014-06-19 21:13:55 +09:00
license Introduce TextHeaders and AsciiString 2014-06-14 15:36:19 +09:00
microbench Fix the inconsistencies between performance tests in ByteBufAllocatorBenchmark 2014-06-21 13:28:02 +09:00
tarball Update the version to 4.1.0.Alpha1-SNAPSHOT 2014-02-13 18:32:26 -08:00
testsuite Introduce MessageAggregator and DecoderResultProvider 2014-06-05 16:51:14 +09:00
transport [#2589] LocalServerChannel.doClose() throws NPE when localAddress == null 2014-06-20 20:13:23 +02:00
transport-native-epoll Make sure OpenSslEngine is tested against transport-native-epoll 2014-06-21 18:28:54 +09:00
transport-rxtx Synchronized between 4.1 and master again (part 2) 2014-04-25 15:06:26 +09:00
transport-sctp Synchronized between 4.1 and master again (part 2) 2014-04-25 15:06:26 +09:00
transport-udt Synchronized between 4.1 and master again (part 2) 2014-04-25 15:06:26 +09: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 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 Introduce TextHeaders and AsciiString 2014-06-14 15:36:19 +09:00
pom.xml Add MQTT protocol codec 2014-06-21 16:52:10 +09:00
README.md Synchronized between 4.1 and master 2014-04-25 00:38:02 +09:00
run-example.sh Overall refactoring of the STOMP codec 2014-06-04 17:09:42 +09: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 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.