andreacavalli/netty5
1
0
Fork 0
Code Issues Pull Requests Projects Releases Wiki Activity
8,317 Commits 27 Branches 234 Tags 84 MiB
Java 99.8%
Shell 0.1%
452fd36240
Go to file
Scott Mitchell 452fd36240 ByteBufs which are not resizable should not throw in ensureWritable(int,boolean) 
Motivation:
ByteBuf#ensureWritable(int,boolean) returns an int indicating the status of the resize operation. For buffers that are unmodifiable or cannot be resized this method shouldn't throw but just return 1.
ByteBuf#ensureWriteable(int) should throw unmodifiable buffers.

Modifications:
- ReadOnlyByteBuf should be updated as described above.
- Add a unit test to SslHandler which verifies the read only buffer can be tolerated in the aggregation algorithm.

Result:
Fixes https://github.com/netty/netty/issues/7002.
2017-07-22 08:44:48 -07:00
.github Use GitHub Issue/PR Template Feature 2016-12-07 11:40:26 -08:00
all [maven-release-plugin] prepare for next development iteration 2017-07-06 13:24:06 +02:00
bom Correct typo in artifactId of dependency in bom pom.xml 2017-07-19 14:20:11 +02:00
buffer ByteBufs which are not resizable should not throw in ensureWritable(int,boolean) 2017-07-22 08:44:48 -07:00
codec Fix #6969: Do not reset the states while streaming Json array 2017-07-17 10:42:54 +02:00
codec-dns [maven-release-plugin] prepare for next development iteration 2017-07-06 13:24:06 +02:00
codec-haproxy [maven-release-plugin] prepare for next development iteration 2017-07-06 13:24:06 +02:00
codec-http Fix flacky multipart test introduced by 08748344d8. 2017-07-21 14:28:32 +02:00
codec-http2 HTTP/2 enforce HTTP message flow 2017-07-19 13:37:23 -07:00
codec-memcache [maven-release-plugin] prepare for next development iteration 2017-07-06 13:24:06 +02:00
codec-mqtt MQTT unknown message type isn't handled as decoding error 2017-07-18 15:48:09 +02:00
codec-redis [maven-release-plugin] prepare for next development iteration 2017-07-06 13:24:06 +02:00
codec-smtp Use ByteBuf#writeShort/writeMedium instead of writeBytes 2017-07-10 14:37:41 +02:00
codec-socks [maven-release-plugin] prepare for next development iteration 2017-07-06 13:24:06 +02:00
codec-stomp [maven-release-plugin] prepare for next development iteration 2017-07-06 13:24:06 +02:00
codec-xml [maven-release-plugin] prepare for next development iteration 2017-07-06 13:24:06 +02:00
common Automatically detect shaded packagePrefix 2017-07-19 18:38:02 -07:00
dev-tools [maven-release-plugin] prepare for next development iteration 2017-07-06 13:24:06 +02:00
example Handle handshake failure in Websocket Client example 2017-07-21 07:36:36 +02:00
handler ByteBufs which are not resizable should not throw in ensureWritable(int,boolean) 2017-07-22 08:44:48 -07:00
handler-proxy HttpProxyHandler: allow setting headers 2017-07-06 20:02:06 +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 Use ByteBuf#writeShort/writeMedium instead of writeBytes 2017-07-10 14:37:41 +02:00
resolver [maven-release-plugin] prepare for next development iteration 2017-07-06 13:24:06 +02:00
resolver-dns Increase timeout for DnsNameResolverTest 2017-07-19 07:59:56 +02:00
tarball [maven-release-plugin] prepare for next development iteration 2017-07-06 13:24:06 +02:00
testsuite Update tests to not use TestUtils.getFreePort() and so ensure we not try to use a port that is used by the system in the meantime. 2017-07-20 08:25:37 +02:00
testsuite-autobahn [maven-release-plugin] prepare for next development iteration 2017-07-06 13:24:06 +02:00
testsuite-osgi [maven-release-plugin] prepare for next development iteration 2017-07-06 13:24:06 +02:00
transport Allow to delay registration when creating a EmbeddedChannel 2017-07-19 19:35:03 +02:00
transport-native-epoll Update tests to not use TestUtils.getFreePort() and so ensure we not try to use a port that is used by the system in the meantime. 2017-07-20 08:25:37 +02:00
transport-native-kqueue Update tests to not use TestUtils.getFreePort() and so ensure we not try to use a port that is used by the system in the meantime. 2017-07-20 08:25:37 +02:00
transport-native-unix-common Use 4 spaces and not 2 spaces (cleanup of 3d22b24244) 2017-07-20 10:24:18 +02:00
transport-native-unix-common-tests [maven-release-plugin] prepare for next development iteration 2017-07-06 13:24:06 +02:00
transport-rxtx [maven-release-plugin] prepare for next development iteration 2017-07-06 13:24:06 +02:00
transport-sctp [maven-release-plugin] prepare for next development iteration 2017-07-06 13:24:06 +02:00
transport-udt [maven-release-plugin] prepare for next development iteration 2017-07-06 13:24:06 +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 Use unbounded queues from JCTools 2.0.2 2017-07-10 12:32:15 -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

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.