andreacavalli/netty5
1
0
Fork 0
Code Issues Pull Requests Projects Releases Wiki Activity
6,241 Commits 27 Branches 234 Tags 84 MiB
Java 99.8%
Shell 0.1%
9dd8e19376
Go to file
Matthias Einwag 9dd8e19376 Add a test for handover from HTTP to Websocket 
Motivation:
I was not fully reassured that whether everything works correctly when a websocket client receives the websocket handshake HTTP response and a websocket frame in a single ByteBuf (which can happen when the server sends a response directly or shortly after the connect). In this case some parts of the ByteBuf must be processed by HTTP decoder and the remaining by the websocket decoder.

Modification:
Adding a test that verifies that in this scenaria the handshake and the message are correctly interpreted and delivered by Netty.

Result:
One more test for Netty.
The test succeeds - No problems
2014-10-13 07:19:12 +02:00
all Add HTTP/2 codec to netty-all maven dependency Motivation: 2014-08-18 19:07:49 +02:00
buffer Disable caching of PooledByteBuf for different threads. 2014-09-22 13:39:42 +02:00
codec Fixing bugs in HTTP/2 pipeline exception handling 2014-09-30 16:31:42 -07:00
codec-dns Fix buffer leaks in DnsResponseDecoder and DnsResponseDecoderTest 2014-08-04 14:05:02 +02:00
codec-haproxy Fix NPE problems 2014-07-20 12:55:08 +02:00
codec-http Add a test for handover from HTTP to Websocket 2014-10-13 07:19:12 +02:00
codec-http2 NullPointerException fix in http/2 codec 2014-10-09 18:13:57 -04:00
codec-memcache Fix most inspector warnings 2014-07-02 19:04:11 +09:00
codec-mqtt Change client id validation range in codec-mqtt 2014-10-13 07:17:40 +02:00
codec-socks codec-socks test cleanup 2014-08-20 06:54:55 +02:00
codec-stomp Fix a resource leak in StompSubframeAggregatorTest 2014-08-11 10:46:17 -07:00
common Fixing bugs in HTTP/2 pipeline exception handling 2014-09-30 16:31:42 -07:00
example Adding a benchmark for websockets 2014-10-13 06:36:03 +02:00
handler Change the operator order of TrafficCounter to calculate the throughput to get the correct result 2014-10-01 06:42:41 +02:00
license Implemented LZMA frame encoder 2014-09-15 15:14:15 +02:00
microbench IPv6 address to string rfc5952 2014-09-22 20:30:14 -04:00
tarball [maven-release-plugin] prepare for next development iteration 2013-12-22 22:06:15 +09:00
testsuite Shutdown Executor on MultithreadEventLoopGroup shutdown. Fixes #2837 2014-09-12 12:17:29 +09:00
transport Improve error reporting in SingleThreadEventLoopTest. Fixes #2894 2014-09-20 15:29:43 -04:00
transport-native-epoll [#2926] Fix 1 byte memory leak in native transport 2014-09-22 15:12:20 +02:00
transport-rxtx Fix most inspector warnings 2014-07-02 19:04:11 +09:00
transport-sctp Allow to obtain RecvByteBufAllocator.Handle to allow more flexible implementations 2014-08-12 06:54:29 +02:00
transport-udt Shutdown Executor on MultithreadEventLoopGroup shutdown. Fixes #2837 2014-09-12 12:17:29 +09:00
.fbprefs Updated Find Bugs configuration 2009-03-04 10:33:09 +00:00
.gitignore Exclude bin directory from git Motivation: 2014-08-27 06:33:22 +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:17:58 +09:00
LICENSE.txt Relicensed to Apache License v2 2009-08-28 07:15:49 +00:00
NOTICE.txt Implemented LZMA frame encoder 2014-09-15 15:14:15 +02:00
pom.xml Implemented LZMA frame encoder 2014-09-15 15:14:15 +02:00
README.md Add a link to the 'native transports' page 2014-07-21 12:10:16 -07:00
run-example.sh ALPN java implementation 2014-08-30 13:41:07 -04: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 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.