Go to file
Robert.Panzer 01c3fd3ace Add support for byte order to LengthFieldPrepender
Motivation:

While the LengthFieldBasedFrameDecoder supports a byte order the LengthFieldPrepender does not.
That means that I can simply add a LengthFieldBasedFrameDecoder with ByteOrder.LITTLE_ENDIAN to my pipeline
but have to write my own Encoder to write length fields in little endian byte order.

Modifications:

Added a constructor that takes a byte order and all other parameters.
All other constructors delegate to this one with ByteOrder.BIG_ENDIAN.
LengthFieldPrepender.encode() uses this byte order to write the length field.

Result:

LengthFieldPrepender will write the length field in the defined byte order.
2015-03-13 19:30:49 +01:00
all [maven-release-plugin] prepare for next development iteration 2015-03-02 01:31:30 -05:00
buffer Updates the javadoc of Unpooled to remove mention to methods it does not provide 2015-03-04 12:03:50 +09:00
codec Add support for byte order to LengthFieldPrepender 2015-03-13 19:30:49 +01:00
codec-http Add unit to maxContentLength javadoc of HttpObjectAggregator 2015-03-05 20:54:52 +01:00
codec-socks [maven-release-plugin] prepare for next development iteration 2015-03-02 01:31:30 -05:00
common Respect -Djava.net.preferIPv4Stack when using epoll transport 2015-03-11 02:49:33 +01:00
example [maven-release-plugin] prepare for next development iteration 2015-03-02 01:31:30 -05:00
handler Add a new constructor without handler parameter to TrafficCounter 2015-03-10 11:26:41 +09:00
license Remove license of deque as we not use it anymore 2014-08-04 12:21:33 +02:00
microbench [maven-release-plugin] prepare for next development iteration 2015-03-02 01:31:30 -05:00
tarball [maven-release-plugin] prepare for next development iteration 2015-03-02 01:31:30 -05:00
testsuite [maven-release-plugin] prepare for next development iteration 2015-03-02 01:31:30 -05:00
testsuite-osgi [maven-release-plugin] prepare for next development iteration 2015-03-02 01:31:30 -05:00
transport Fix SocketException in NioSocketChannelUnsafe.closeExecutor() 2015-03-05 15:17:43 +09:00
transport-native-epoll First load RuntimeException to prevent segfault on error 2015-03-13 18:28:32 +01:00
transport-rxtx [maven-release-plugin] prepare for next development iteration 2015-03-02 01:31:30 -05:00
transport-sctp [maven-release-plugin] prepare for next development iteration 2015-03-02 01:31:30 -05:00
transport-udt [maven-release-plugin] prepare for next development iteration 2015-03-02 01:31:30 -05: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 Remove license of deque as we not use it anymore 2014-08-04 12:21:33 +02:00
pom.xml [maven-release-plugin] prepare for next development iteration 2015-03-02 01:31:30 -05:00
README.md Add a link to the 'native transports' page 2014-07-21 12:54:43 -07:00
run-example.sh Add logLevel property to enable different log levels for the examples. 2014-11-21 10:48:13 +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 major versions takes place in each branch whose name is identical to its major version number. For example, the development of 3.x and 4.x resides in the branch '3' and the branch '4' respectively.