Go to file
Idel Pivnitskiy 37c7766878 Fixes for compression codecs
Motivation:

Fixed founded mistakes in compression codecs.

Modifications:

- Changed return type of ZlibUtil.inflaterException() from CompressionException to DecompressionException
- Updated @throws in javadoc of JZlibDecoder to throw DecompressionException instead of CompressionException
- Fixed JdkZlibDecoder to throw DecompressionException instead of CompressionException
- Removed unnecessary empty lines in JdkZlibEncoder and JZlibEncoder
- Removed public modifier from Snappy class
- Added MAX_UNCOMPRESSED_DATA_SIZE constant in SnappyFramedDecoder
- Used in.readableBytes() instead of (in.writerIndex() - in.readerIndex()) in SnappyFramedDecoder
- Added private modifier for enum ChunkType in SnappyFramedDecoder
- Fixed potential bug (sum overflow) in Bzip2HuffmanAllocator.first(). For more info, see http://googleresearch.blogspot.ru/2006/06/extra-extra-read-all-about-it-nearly.html

Result:

Fixed sum overflow in Bzip2HuffmanAllocator, improved exceptions in ZlibDecoder implementations, hid Snappy class
2014-07-20 09:32:26 +02:00
all Add MQTT protocol codec 2014-06-21 16:51:37 +09:00
buffer Small performance improvements 2014-07-20 09:24:56 +02:00
codec Fixes for compression codecs 2014-07-20 09:32:26 +02:00
codec-dns Fix most inspector warnings 2014-07-02 19:04:11 +09:00
codec-haproxy Fix test failures due to incorrect validation 2014-06-21 17:11:08 +09:00
codec-http Small performance improvements 2014-07-20 09:24:56 +02:00
codec-http2 Upgrade to HTTP/2 draft 13 2014-07-08 21:10:46 +02:00
codec-memcache Fix most inspector warnings 2014-07-02 19:04:11 +09:00
codec-mqtt Mqtt -> MQTT 2014-06-21 17:14:20 +09:00
codec-socks Fix most inspector warnings 2014-07-02 19:04:11 +09:00
codec-stomp Small performance improvements 2014-07-20 09:24:56 +02:00
common Small performance improvements 2014-07-20 09:24:56 +02:00
example Add WebSocket Extension handlers for client and server. 2014-07-09 16:28:40 +02:00
handler [#2618] Introduce ChannelPromise.unvoid() and ChannelFuture.isVoid() 2014-07-03 14:16:46 +02:00
license Implemented a Bzip2Encoder 2014-07-17 16:19:59 +02:00
microbench Fix the inconsistencies between performance tests in ByteBufAllocatorBenchmark 2014-06-21 13:27:28 +09:00
tarball [maven-release-plugin] prepare for next development iteration 2013-12-22 22:06:15 +09:00
testsuite [#2647] Respect IOV_MAX when call writev in native transport 2014-07-09 12:18:48 +02:00
transport [#2665] Continue writing on IOException when using DatagramChannel 2014-07-18 12:49:56 +02:00
transport-native-epoll [#2667] Write until EAGAIN in native transport and only call setEpollOut() in this case 2014-07-18 20:45:18 +02:00
transport-rxtx Fix most inspector warnings 2014-07-02 19:04:11 +09:00
transport-sctp Fix most inspector warnings 2014-07-02 19:04:11 +09:00
transport-udt Fix most inspector warnings 2014-07-02 19:04:11 +09: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:34:51 +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:17:58 +09:00
LICENSE.txt Relicensed to Apache License v2 2009-08-28 07:15:49 +00:00
NOTICE.txt Implemented a Bzip2Encoder 2014-07-17 16:19:59 +02:00
pom.xml Implemented LZF compression codec 2014-07-17 07:18:53 +02:00
README.md Synchronized between 4.1 and master (part 3) 2014-04-25 16:17:16 +09:00
run-example.sh Overall refactoring of the STOMP codec 2014-06-04 17:09:11 +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.