andreacavalli/netty5
1
0
Fork 0
Code Issues Pull Requests Projects Releases Wiki Activity
5,805 Commits 27 Branches 234 Tags 84 MiB
Java 99.8%
Shell 0.1%
48f2e705d9
Go to file
Norman Maurer 48f2e705d9 Resurrect channel deregistration and constructor changes 
Motivation:

Due to the complexity of handling deregistration and re-registration of
a channel, we previously decided to remove the deregister() operation
completely to simplify our code.  However, we realized that it shouldn't
be that complicated to implement it during our discussion about making
I/O scheduling more flexible and more customizable [1], and thus the
removal of deregistration and re-registration is unnecessary now.

Modification:

- Revert commit c149f4bcc0
- Revert commit e743a27e75
- Make some additional adjustments

Result:

- deregister(), fireChannelUnregistered(), and channelRegistered() were
  added back..
- Channel constructors do not require an EventLoop anymore.

[1] https://github.com/netty/netty/issues/2250
2014-04-24 20:54:50 +09: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 Fix chunk type for stream identifier 2014-04-19 21:06:46 +02:00
codec-http [#2401] Improve documentation of HttpObjectAggregator 2014-04-17 15:42:47 +02:00
codec-http2 HTTP2 server should not send preface string 2014-04-17 21:51:34 +02:00
codec-memcache [codec-memcache] Avoid NPE on channelInactive. 2014-04-23 11:41:07 +02:00
codec-socks Fix an inspector warning 2014-02-06 15:03:03 -08:00
common Stop ThreadLocalRandom's initial seed generation immediately on interruption 2014-04-20 17:55:38 +09:00
example HTTP2 server should not send preface string 2014-04-17 21:51:34 +02:00
handler Resurrect channel deregistration and constructor changes 2014-04-24 20:54:50 +09: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 Resurrect channel deregistration and constructor changes 2014-04-24 20:54:50 +09:00
transport Resurrect channel deregistration and constructor changes 2014-04-24 20:54:50 +09:00
transport-native-epoll Resurrect channel deregistration and constructor changes 2014-04-24 20:54:50 +09:00
transport-rxtx Resurrect channel deregistration and constructor changes 2014-04-24 20:54:50 +09:00
transport-sctp Resurrect channel deregistration and constructor changes 2014-04-24 20:54:50 +09:00
transport-udt Resurrect channel deregistration and constructor changes 2014-04-24 20:54:50 +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 Mark sun.nio.ch as optional 2014-04-23 10:37:39 +02: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.