andreacavalli/netty5
1
0
Fork 0
Code Issues Pull Requests Projects Releases Wiki Activity
6,635 Commits 27 Branches 234 Tags 84 MiB
Java 99.8%
Shell 0.1%
f6bfecc822
Go to file
Scott Mitchell f6bfecc822 Revert JDK GCM direct buffer crash workaround 
Motivation:
Commit 108dc23cab introduced a workaround due to a JDK crash when GCM cipher was used during an unwrap operation. Attempting to reproduce this issue with the latest JDK (1.8.0_72-b15) demonstrate that this issue no longer exists while it can be reliably reproduced on earlier JDKs (1.8.0_25-b17 and earlier)

Modifications:
- Remove the copy-to-heap-buffer workaround for JDK engine

Result:
Fixes https://github.com/netty/netty/issues/3256
2016-02-17 19:53:30 -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 Ensure read components can be discarded when COMPOSITE_CUMULATOR is used. 2016-02-17 19:51:29 -08:00
codec-haproxy [maven-release-plugin] prepare for next development iteration 2016-01-29 09:57:10 +01:00
codec-http ByteToMessageDecoder ChannelInputShutdownEvent support 2016-02-12 16:29:00 -08:00
codec-socks [maven-release-plugin] prepare for next development iteration 2016-01-29 09:57:10 +01:00
common Leak Detector disclosing when records dropped 2016-02-12 09:58:10 -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 Revert JDK GCM direct buffer crash workaround 2016-02-17 19:53:30 -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 Upgrade to netty-tcnative-1.1.33.Fork13 2016-02-17 08:17:13 -08:00
testsuite-osgi [maven-release-plugin] prepare for next development iteration 2016-01-29 09:57:10 +01:00
transport Ensure handlerAdded(...) and handlerRemoved(...) is always called from the right thread 2016-02-12 14:30:33 -08: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 Upgrade to netty-tcnative-1.1.33.Fork13 2016-02-17 08:17:13 -08: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.