Go to file
Norman Maurer 7922757575 Allow to access memoryAddress of wrapped ByteBuf for ReadOnlyByteBuf
Motivation:

We should allow to access the memoryAddress of the wrapped ByteBuf when using ReadOnlyByteBuf for peformance reasons. If a user act on a memoryAddress its his responsible anyway to do nothing "stupid".

Modifications:

Delegate to wrapped ByteBuf.

Result:

Less performance overhead for various operations and also when writing to a native transport (which needs the memoryAddress).
2017-06-07 18:45:26 +02:00
.github Use GitHub Issue/PR Template Feature 2016-12-07 11:40:26 -08:00
all Correctly exclude netty-tcnative classes from the all jar. 2017-05-30 16:00:01 -07:00
bom Correctly include native modules 2017-05-18 07:03:28 +02:00
buffer Allow to access memoryAddress of wrapped ByteBuf for ReadOnlyByteBuf 2017-06-07 18:45:26 +02:00
codec JdkZlibDecoder and JZlibDecoder consistency 2017-06-06 14:18:10 -07:00
codec-dns [maven-release-plugin] prepare for next development iteration 2017-05-11 16:00:55 +02:00
codec-haproxy Added PROXY Protocol TLV support 2017-06-07 09:09:29 -07:00
codec-http Move QueryStringDecoder.decodeHexByte into ByteBufUtil 2017-06-07 09:27:36 -07:00
codec-http2 [maven-release-plugin] prepare for next development iteration 2017-05-11 16:00:55 +02:00
codec-memcache [maven-release-plugin] prepare for next development iteration 2017-05-11 16:00:55 +02:00
codec-mqtt Issue №6802. Not specified field in MQTT codec (#6807) 2017-06-05 13:21:49 -07:00
codec-redis RedisDecoder infinite loop 2017-05-30 08:53:36 -07:00
codec-smtp Don't add null to SmtpResponse.details() 2017-05-23 19:17:59 +02:00
codec-socks [maven-release-plugin] prepare for next development iteration 2017-05-11 16:00:55 +02:00
codec-stomp [maven-release-plugin] prepare for next development iteration 2017-05-11 16:00:55 +02:00
codec-xml [maven-release-plugin] prepare for next development iteration 2017-05-11 16:00:55 +02:00
common Add explicit message when noexec prevents library loading. 2017-06-07 09:20:05 -07:00
dev-tools [maven-release-plugin] prepare for next development iteration 2017-05-11 16:00:55 +02:00
example [maven-release-plugin] prepare for next development iteration 2017-05-11 16:00:55 +02:00
handler OpenSslEngine return NEED_WRAP if the destination buffered filled 2017-06-02 07:47:35 -07:00
handler-proxy [maven-release-plugin] prepare for next development iteration 2017-05-11 16:00:55 +02:00
license Remove reference to akka code and ArrayDeque which is not part of netty anymore 2017-03-07 21:30:51 +01:00
microbench Optimizations in NetUtil 2017-05-18 16:42:22 -07:00
resolver [maven-release-plugin] prepare for next development iteration 2017-05-11 16:00:55 +02:00
resolver-dns UnixResolverDnsServerAddressStreamProvider default name server selection and ordering bug 2017-05-18 15:14:58 -07:00
tarball Add uber-staging and uber-snapshot profile that can be used to generate uber all jars. 2017-05-16 08:28:23 +02:00
testsuite Fix handle of ByteBuf with multi nioBuffer in EpollDatagramChannel and KQueueDatagramChannel 2017-05-26 07:56:34 +02:00
testsuite-autobahn [maven-release-plugin] prepare for next development iteration 2017-05-11 16:00:55 +02:00
testsuite-osgi [maven-release-plugin] prepare for next development iteration 2017-05-11 16:00:55 +02:00
transport Not add ChannelHandler to ChannelPipeline once the pipeline was destroyed. 2017-05-31 07:37:39 +02:00
transport-native-epoll Fix handle of ByteBuf with multi nioBuffer in EpollDatagramChannel and KQueueDatagramChannel 2017-05-26 07:56:34 +02:00
transport-native-kqueue Fix handle of ByteBuf with multi nioBuffer in EpollDatagramChannel and KQueueDatagramChannel 2017-05-26 07:56:34 +02:00
transport-native-unix-common Correctly parse package-prefix if the jni lib is contained in a path that matches the library name. 2017-05-29 20:09:57 +02:00
transport-native-unix-common-tests Fix handle of ByteBuf with multi nioBuffer in EpollDatagramChannel and KQueueDatagramChannel 2017-05-26 07:56:34 +02:00
transport-rxtx [maven-release-plugin] prepare for next development iteration 2017-05-11 16:00:55 +02:00
transport-sctp Fix parameter order in SctpOutboundByteStreamHandler. 2017-05-25 09:28:28 +02:00
transport-udt [maven-release-plugin] prepare for next development iteration 2017-05-11 16:00:55 +02:00
.fbprefs Updated Find Bugs configuration 2009-03-04 10:33:09 +00:00
.gitignore Use shaded dependency on JCTools instead of copy and paste 2016-06-10 13:19:45 +02: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 Remove reference to akka code and ArrayDeque which is not part of netty anymore 2017-03-07 21:30:51 +01:00
pom.xml Add explicit message when noexec prevents library loading. 2017-06-07 09:20:05 -07:00
README.md Updating Branches to look section to match the current branching structure of the project 2016-03-10 22:08:01 +01:00
run-example.sh Add UptimeServer and adjust UptimeClient's code style. 2017-04-28 07:41:07 +02: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

Development of all 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.