Go to file
Norman Maurer 6c24dd4d8f Pass struct's per pointer to eliminate memory copy.
Motivation:

Before struct's were passed per value and not pointer. This did enforce a memory copy which is not needed.

Modifications:

- Use "const struct....*" as replacement

Result:

No more unnecessary memory copies
2015-02-27 20:58:26 +01:00
all Fix missing version properties of transport-epoll in all-in-one JAR 2014-10-21 22:36:10 +09:00
buffer Ensure CompositeByteBuf.addComponent* handles buffer in consistent way and not causes leaks 2015-02-12 16:09:41 +01:00
codec Suggestion for supporting single header fields. 2015-02-18 10:54:15 +01:00
codec-dns Add EDNS support to DnsQueryEncoder 2014-10-16 17:05:08 +09:00
codec-haproxy [maven-release-plugin] prepare for next development iteration 2014-08-16 03:27:42 +09:00
codec-http When null origin is supported then credentials header must not be set. 2015-02-18 16:06:30 +01:00
codec-http2 Removing debugging change from unit test. 2015-02-11 09:07:08 -08:00
codec-memcache Add proxy support for client socket connections 2014-10-14 12:29:08 +09:00
codec-mqtt Fix dependency issues with hamcrest 2014-12-04 17:59:15 +09:00
codec-socks Fixed buffer leaks in DefaultSocks5CommandResponseTest 2015-02-20 16:54:26 +09:00
codec-stomp Headers set/add/contains timeMillis methods 2014-12-06 22:40:28 +09:00
codec-xml Integrate non-blocking XML parser as Netty codec (#2806) 2015-02-19 13:46:14 +01:00
common Allow to use EmbeddedChannel.schedule*(...) 2015-02-20 11:57:32 +01:00
example Revamp io.netty.handler.codec.socksx 2015-02-10 09:14:13 +09:00
handler Various performance optimizations in OpenSslEngine 2015-02-09 06:20:19 +01:00
handler-proxy Revamp io.netty.handler.codec.socksx 2015-02-10 09:14:13 +09:00
license Integrate non-blocking XML parser as Netty codec (#2806) 2015-02-19 13:46:14 +01:00
microbench Fix ByteBufUtilBenchmark on utf8 encodings. 2014-12-31 20:26:42 +09:00
resolver Name resolver API and DNS-based name resolver 2014-10-16 17:05:20 +09:00
resolver-dns Remove thepiratebay.se from the test domain list 2014-12-22 22:35:17 +09:00
tarball [maven-release-plugin] prepare for next development iteration 2014-08-16 03:27:42 +09:00
testsuite Allow to use WebSocketClientHandshaker and WebSocketServerHandshaker with HttpResponse / HttpRequest 2015-02-06 10:46:07 +01:00
testsuite-osgi Add a pax-exam based OSGi test suite 2015-02-18 16:00:15 +01:00
transport typo_fix in the comment 2015-02-25 20:30:40 +01:00
transport-native-epoll Pass struct's per pointer to eliminate memory copy. 2015-02-27 20:58:26 +01:00
transport-rxtx [maven-release-plugin] prepare for next development iteration 2014-08-16 03:27:42 +09:00
transport-sctp [maven-release-plugin] prepare for next development iteration 2014-08-16 03:27:42 +09:00
transport-udt Fix typo in param name 2015-01-16 20:30:35 +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 Integrate non-blocking XML parser as Netty codec (#2806) 2015-02-19 13:46:14 +01:00
pom.xml Upgrading HTTP/2 hpack to latest version 2015-02-24 07:05:49 +01:00
README.md Add a link to the 'native transports' page 2014-07-21 12:54:24 -07:00
run-example.sh Add logLevel property to enable different log levels for the examples. 2014-11-21 10:48:57 +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.