andreacavalli/netty5
1
0
Fork 0
Code Issues Pull Requests Projects Releases Wiki Activity
5,728 Commits 27 Branches 234 Tags 84 MiB
Java 99.8%
Shell 0.1%
787a85f9f1
Go to file
Norman Maurer 787a85f9f1 Remove ContinuationWebSocketFrame.aggregatedText() 
Motivation:
Before we aggregated the full text in the WebSocket08FrameDecoder just to fill in the ContinuationWebSocketFrame.aggregatedText(). The problem was that there was no upper-limit and so it would be possible to see an OOME if the remote peer sends a TextWebSocketFrame + a never ending stream of ContinuationWebSocketFrames. Furthermore the aggregation does not really belong in the WebSocket08FrameDecoder, as we provide an extra ChannelHandler for this anyway (WebSocketFrameAggregator).

Modification:
Remove the ContinuationWebSocketFrame.aggregatedText() method and corresponding constructor. Also refactored WebSocket08FrameDecoder a bit to me more efficient which is now possible as we not need to aggregate here.

Result:
No more risk of OOME because of frames.
2014-04-30 14:40:52 +02:00
all [maven-release-plugin] prepare for next development iteration 2014-04-01 07:21:40 +02:00
buffer Fix error that causes (up to) double memory usage 2014-04-15 07:02:49 +02:00
codec Fix chunk type for stream identifier 2014-04-19 21:02:34 +02:00
codec-http Remove ContinuationWebSocketFrame.aggregatedText() 2014-04-30 14:40:52 +02:00
codec-socks Correctly handle SocksCmdResponse. Related to #2428 2014-04-30 10:42:46 +02:00
common Code clean-up 2014-04-25 17:44:15 +09:00
example SPDY: refactor frame codec implementation 2014-04-15 20:05:05 +02:00
handler Correctly write pending data after ssl handshake completes. Related to [#2437] 2014-04-30 14:23:03 +02:00
license [#1259] Add optimized queue for SCMP pattern and use it in NIO and native transport 2014-02-27 11:44:06 +01:00
microbench [maven-release-plugin] prepare for next development iteration 2014-04-01 07:21:40 +02:00
tarball [maven-release-plugin] prepare for next development iteration 2014-04-01 07:21:40 +02:00
testsuite Correctly write pending data after ssl handshake completes. Related to [#2437] 2014-04-30 14:23:03 +02:00
transport Not cause busy loop when interrupt Thread of NioEventLoop 2014-04-28 08:05:46 +02:00
transport-native-epoll [#2414] Fix IllegalStateException when try to configure AbstractEpollChannel once it is deregistered 2014-04-22 10:14:31 +02:00
transport-rxtx [maven-release-plugin] prepare for next development iteration 2014-04-01 07:21:40 +02:00
transport-sctp [#2375] [#2404] Fix bug in respecting ChannelConfig.setAutoRead(false) and also fix Channel.read() for OIO 2014-04-17 07:37:34 +02:00
transport-udt [maven-release-plugin] prepare for next development iteration 2014-04-01 07:21:40 +02:00
.fbfilter.xml Update license headers 2012-06-04 13:31:44 -07:00
.fbprefs Updated Find Bugs configuration 2009-03-04 10:33:09 +00:00
.gitignore Format and partially describe Gitignore 2013-12-10 07:04:38 +01: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 [#1259] Add optimized queue for SCMP pattern and use it in NIO and native transport 2014-02-27 11:44:06 +01:00
pom.xml Mark sun.nio.ch as optional 2014-04-23 10:34:45 +02:00
README.md Update README.md 2014-01-16 14:38:36 +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

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.