andreacavalli/netty5
1
0
Fork 0
Code Issues Pull Requests Projects Releases Wiki Activity
5,776 Commits 27 Branches 234 Tags 84 MiB
Java 99.8%
Shell 0.1%
350c8ef42a
Go to file
Jeff Pinner 350c8ef42a SPDY: refactor frame codec implementation 
Motivation:

Currently, the SPDY frame encoding and decoding code is based upon
the ChannelHandler abstraction. This requires maintaining multiple
versions for 3.x and 4.x (and possibly 5.x moving forward).

Modifications:

The SPDY frame encoding and decoding code is separated from the
ChannelHandler and SpdyFrame abstractions. Also test coverage is
improved.

Result:

SpdyFrameCodec now implements the ChannelHandler abstraction and is
responsible for creating and handling SpdyFrame objects.
2014-04-15 18:42:08 +02:00
all Ensure native transport is included in all and tarball 2014-02-17 22:46:33 +01:00
buffer Fix error that causes (up to) double memory usage 2014-04-15 06:57:19 +02:00
codec [#2353] Use a privileged block to get ClassLoader and System property if needed 2014-04-08 14:13:49 +02:00
codec-http SPDY: refactor frame codec implementation 2014-04-15 18:42:08 +02:00
codec-http2 Adding support for HTTP/2 initialization handshake. 2014-04-11 06:50:42 +02:00
codec-memcache [codec-memcache] Simplify object hierachy and remove Headers. 2014-03-04 13:04:44 +01:00
codec-socks Fix an inspector warning 2014-02-06 15:03:03 -08:00
common [#2353] Use a privileged block to get ClassLoader and System property if needed 2014-04-08 14:13:49 +02:00
example SPDY: refactor frame codec implementation 2014-04-15 18:42:08 +02:00
handler [#2353] Use a privileged block to get ClassLoader and System property if needed 2014-04-08 14:13:49 +02:00
license [#1259] Add optimized queue for SCMP pattern and use it in NIO and native transport 2014-02-27 13:56:15 +01:00
microbench Upgrade JMH to 0.4.1 and make use of @Params. 2014-02-23 16:39:15 +01:00
tarball [maven-release-plugin] prepare for next development iteration 2013-12-22 22:06:15 +09:00
testsuite SPDY: refactor frame codec implementation 2014-04-15 18:42:08 +02:00
transport [#2390] Minimize memory usage of NioDatagramChannel 2014-04-15 06:56:33 +02:00
transport-native-epoll [#2371] Fix Potential data corruption in EpollSocketChannel when writing to the Channel 2014-04-09 14:26:04 +02:00
transport-rxtx Apply receive timeout to commPort when using RxtxChannel. Part of [#1390] 2014-02-23 16:35:35 +01:00
transport-sctp Directly use memory addresses for gathering writes to reduce gc pressure. Part of [#2239] 2014-02-21 14:16:37 +01:00
transport-udt Enable a user specify an arbitrary information with ReferenceCounted.touch() 2014-01-29 11:44:59 +09: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:03:43 +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:17:58 +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 13:56:15 +01:00
pom.xml First cut of frame encoding/decoding and session management for HTTP2 2014-03-27 10:40:47 -07:00
README.md Fix the 'branches to look' section 2014-01-16 14:37:54 +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 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.