andreacavalli/netty5
1
0
Fork 0
Code Issues Pull Requests Projects Releases Wiki Activity
6,629 Commits 27 Branches 234 Tags 84 MiB
Java 99.8%
Shell 0.1%
8ddba82fce
Go to file
Scott Mitchell 8ddba82fce ByteBufUtil.writeUtf8 not consistent with String.getBytes(Charset) 
Motivation:
f750d6e36c added support for surrogates in the writeUtf8 conversion. However exceptions are thrown if invalid input is detected, but the JDK (and slow path of writeUtf8) uses a replacement character and does not throw. We should behave the same way.

Modificiations:
- Don't throw in ByteBufUtil.writeUtf8, and instead use a replacement character consistent with the JDK

Result:
ByteBufUtil.writeUtf8 behavior is consistent with the JDK UTF_8 conversion.
2016-02-11 08:27:22 -08:00
all [maven-release-plugin] prepare for next development iteration 2016-01-29 09:57:10 +01:00
buffer ByteBufUtil.writeUtf8 not consistent with String.getBytes(Charset) 2016-02-11 08:27:22 -08:00
codec [#4793] Correctly add newlines when encode base64 2016-02-06 09:56:32 +01:00
codec-haproxy [maven-release-plugin] prepare for next development iteration 2016-01-29 09:57:10 +01:00
codec-http HttpObjectDecoder configurable initial buffer size 2016-02-07 21:27:40 -08:00
codec-socks [maven-release-plugin] prepare for next development iteration 2016-01-29 09:57:10 +01:00
common Add unescapeCsv to StringUtil 2016-02-08 14:35:44 -08:00
example Allow to specify tcnative artifactId and verion to allow run tests easily with different tcnative flavors 2016-01-29 22:25:03 +01:00
handler Allow InputStreams for key/trust managers in SslContextBuilder 2016-02-05 14:40:16 -08:00
license Let PoolThreadCache work even if allocation and deallocation Thread are different 2015-05-27 14:35:22 +02:00
microbench [maven-release-plugin] prepare for next development iteration 2016-01-29 09:57:10 +01:00
tarball [maven-release-plugin] prepare for next development iteration 2016-01-29 09:57:10 +01:00
testsuite Allow to specify tcnative artifactId and verion to allow run tests easily with different tcnative flavors 2016-01-29 22:25:03 +01:00
testsuite-osgi [maven-release-plugin] prepare for next development iteration 2016-01-29 09:57:10 +01:00
transport [#4805] Respect isAutoRead() once re-register Channel 2016-02-04 15:34:06 +01:00
transport-native-epoll Remove invalid return 2016-02-10 16:48:17 -08:00
transport-rxtx [maven-release-plugin] prepare for next development iteration 2016-01-29 09:57:10 +01:00
transport-sctp [maven-release-plugin] prepare for next development iteration 2016-01-29 09:57:10 +01:00
transport-udt [maven-release-plugin] prepare for next development iteration 2016-01-29 09:57:10 +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:37:12 +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:18:14 +09:00
LICENSE.txt Relicensed to Apache License v2 2009-08-28 07:15:49 +00:00
NOTICE.txt Let PoolThreadCache work even if allocation and deallocation Thread are different 2015-05-27 14:35:22 +02:00
pom.xml Add maven profile to run tests with -Dio.netty.noUnsafe=true 2016-02-06 09:57:52 +01:00
README.md Fix the 'branches to look' section 2015-10-27 13:58:06 +01:00
run-example.sh Add logLevel property to enable different log levels for the examples. 2014-11-21 10:48:13 +09: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 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.