Go to file
Xiaoyan Lin e2d4e22243 Add CharsetUtil.encoder/decoder() methods
Motivation:

See #3321

Modifications:

1. Add CharsetUtil.encoder/decoder() methods
2. Deprecate CharsetUtil.getEncoder/getDecoder() methods

Result:

Users can use new CharsetUtil.encoder/decoder() to specify error actions
2016-03-07 10:48:31 +00:00
all Add xml-maven-plugin to check indentation and fix violations 2016-02-29 09:46:32 +01:00
buffer Add CharsetUtil.encoder/decoder() methods 2016-03-07 10:48:31 +00:00
codec [#4386] ByteToMessage.decodeLast(...) should not call decode(...) if buffer is empty. 2016-03-01 08:42:26 +01:00
codec-dns [maven-release-plugin] prepare for next development iteration 2016-02-19 23:00:11 +01:00
codec-haproxy [maven-release-plugin] prepare for next development iteration 2016-02-19 23:00:11 +01:00
codec-http Handle only those http requests that equal to adjusted websocket path 2016-03-04 08:36:14 +01:00
codec-http2 HTTP/2 Reduce Log Level 2016-03-04 17:25:04 -08:00
codec-memcache [maven-release-plugin] prepare for next development iteration 2016-02-19 23:00:11 +01:00
codec-mqtt [maven-release-plugin] prepare for next development iteration 2016-02-19 23:00:11 +01:00
codec-socks Add CharsetUtil.encoder/decoder() methods 2016-03-07 10:48:31 +00:00
codec-stomp [maven-release-plugin] prepare for next development iteration 2016-02-19 23:00:11 +01:00
codec-xml [maven-release-plugin] prepare for next development iteration 2016-02-19 23:00:11 +01:00
common Add CharsetUtil.encoder/decoder() methods 2016-03-07 10:48:31 +00:00
example Handle only those http requests that equal to adjusted websocket path 2016-03-04 08:36:14 +01:00
handler Just a couple of minor javadoc fixes 2016-03-06 17:45:48 +01:00
handler-proxy [maven-release-plugin] prepare for next development iteration 2016-02-19 23:00:11 +01:00
license added support for Protobuf codec nano runtime 2016-01-19 21:39:17 +01:00
microbench Add xml-maven-plugin to check indentation and fix violations 2016-02-29 09:46:32 +01:00
resolver [maven-release-plugin] prepare for next development iteration 2016-02-19 23:00:11 +01:00
resolver-dns Remove a unused import 2016-02-24 11:17:35 +09:00
tarball [maven-release-plugin] prepare for next development iteration 2016-02-19 23:00:11 +01:00
testsuite [maven-release-plugin] prepare for next development iteration 2016-02-19 23:00:11 +01:00
testsuite-osgi Add xml-maven-plugin to check indentation and fix violations 2016-02-29 09:46:32 +01:00
transport Fork SpscLinkedQueue and SpscLinkedAtomicQueue from JCTools 2016-02-22 15:55:52 +01:00
transport-native-epoll Use smaller connect timeout to speed up tests. 2016-03-06 17:47:38 +01:00
transport-rxtx [maven-release-plugin] prepare for next development iteration 2016-02-19 23:00:11 +01:00
transport-sctp Add xml-maven-plugin to check indentation and fix violations 2016-02-29 09:46:32 +01:00
transport-udt [maven-release-plugin] prepare for next development iteration 2016-02-19 23:00:11 +01: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 added support for Protobuf codec nano runtime 2016-01-19 21:39:17 +01:00
pom.xml Add junit timeout listener to print the full thread dump on test timeout 2016-03-04 10:47:11 +01:00
README.md Fix the 'branches to look' section 2015-10-27 13:59:11 +01:00
run-example.sh Add HTTP/2 Netty tiles example 2015-05-18 14:16:54 -07: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.