andreacavalli/netty5
1
0
Fork 0
Code Issues Pull Requests Projects Releases Wiki Activity
7,236 Commits 27 Branches 234 Tags 84 MiB
Java 99.8%
Shell 0.1%
aaa015553b
Go to file
Scott Mitchell aaa015553b Correct usages of internalNioBuffer 
Motivation:
There are numerous usages of internalNioBuffer which hard code 0 for the index when the intention was to use the readerIndex().

Modifications:
- Remove hard coded 0 for the index and use readerIndex()

Result:
We are less susceptible to using the wrong index, and don't make assumptions about the ByteBufAllocator.
2017-03-02 12:52:58 -08:00
.github Use GitHub Issue/PR Template Feature 2016-12-07 11:40:46 -08:00
all [maven-release-plugin] prepare for next development iteration 2017-01-30 17:42:39 +01:00
bom Add a 'bill of materials' project for Maven users 2017-03-01 10:54:02 +01:00
buffer Correct usages of internalNioBuffer 2017-03-02 12:52:58 -08:00
codec Base64 reduce byte manipulation operations 2017-02-22 21:34:20 -08:00
codec-haproxy [maven-release-plugin] prepare for next development iteration 2017-01-30 17:42:39 +01:00
codec-http Correctly build socketaddress string, followup of 8b2badf44f 2017-03-01 20:05:00 +01:00
codec-socks [maven-release-plugin] prepare for next development iteration 2017-01-30 17:42:39 +01:00
common Correctly build socketaddress string, followup of 8b2badf44f 2017-03-01 20:05:00 +01:00
example Cleanup : removed unnecessary 'continue', explicit array creation, unwrapping 2017-02-10 12:25:21 +01:00
handler Correct usages of internalNioBuffer 2017-03-02 12:52:58 -08:00
license Let PoolThreadCache work even if allocation and deallocation Thread are different 2015-05-27 14:35:22 +02:00
microbench Allow to obtain informations of used direct and heap memory for ByteBufAllocator implementations 2017-03-01 18:56:16 +01:00
tarball [maven-release-plugin] prepare for next development iteration 2017-01-30 17:42:39 +01:00
testsuite Make methods 'static' where it missed 2017-02-23 11:23:25 +01:00
testsuite-autobahn Move AutobahnTestsuite to extra module 2017-02-21 10:14:09 +01:00
testsuite-osgi Make netty build work on Java9 2017-02-16 20:27:24 +01:00
transport Correct usages of internalNioBuffer 2017-03-02 12:52:58 -08:00
transport-native-epoll Cleanup EPOLL native exceptions 2017-03-01 05:43:05 -08:00
transport-rxtx [maven-release-plugin] prepare for next development iteration 2017-01-30 17:42:39 +01:00
transport-sctp [maven-release-plugin] prepare for next development iteration 2017-01-30 17:42:39 +01:00
transport-udt Remove annotation from package-info.java as IDEA not like it, cleanup of 4734ef61a5 2017-03-01 21:07:54 +01: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:53:28 +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: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 a 'bill of materials' project for Maven users 2017-03-01 10:54:02 +01:00
README.md Updating Branches to look section to match the current branching structure of the project 2016-03-10 22:09:30 +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

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.