andreacavalli/netty5
1
0
Fork 0
Code Issues Pull Requests Projects Releases Wiki Activity
6,870 Commits 27 Branches 234 Tags 84 MiB
Java 99.8%
Shell 0.1%
58ef38c7f0
Go to file
Norman Maurer 58ef38c7f0 [#5486] Not operate on serial execution assumption when using EventExecutor in the DefaultChannelPipeline. 
Motivation:

In commit f984870ccc I made a change which operated under invalide assumption that tasks executed by an EventExecutor will always be processed in a serial fashion. This is true for SingleThreadEventExecutor sub-classes but not part of the EventExecutor interface contract.

Because of this change implementations of EventExecutor which not strictly execute tasks in a serial fashion may miss events before handlerAdded(...) is called. This is strictly speaking not correct as there is not guarantee in this case that handlerAdded(...) will be called as first task (as there is no ordering guarentee).

Cassandra itself ships such an EventExecutor implementation which has no strict ordering to spread load across multiple threads.

Modifications:

- Add new OrderedEventExecutor interface and let SingleThreadEventExecutor / EventLoop implement / extend it.
- Only expose "restriction" of skipping events until handlerAdded(...) is called for OrderedEventExecutor implementations
- Add ThreadPoolEventExecutor implementation which executes tasks in an unordered fashion. This is used in added unit test but can also be used for protocols which not expose an strict ordering.
- Add unit test.

Result:

Resurrect the possibility to implement an EventExecutor which does not enforce serial execution of events and be able to use it with the DefaultChannelPipeline.
2016-07-07 14:53:33 +02:00
all [maven-release-plugin] prepare for next development iteration 2016-07-01 07:59:55 +02:00
buffer [maven-release-plugin] prepare for next development iteration 2016-07-01 07:59:55 +02:00
codec [maven-release-plugin] prepare for next development iteration 2016-07-01 07:59:55 +02:00
codec-haproxy [maven-release-plugin] prepare for next development iteration 2016-07-01 07:59:55 +02:00
codec-http Fix set100ContinueExpected(...) jsvadoc 2016-07-04 19:05:34 +02:00
codec-socks [maven-release-plugin] prepare for next development iteration 2016-07-01 07:59:55 +02:00
common [#5486] Not operate on serial execution assumption when using EventExecutor in the DefaultChannelPipeline. 2016-07-07 14:53:33 +02:00
example [maven-release-plugin] prepare for next development iteration 2016-07-01 07:59:55 +02:00
handler Add FlushConsolidationHandler which consolidates flush operations as these are expensive 2016-07-07 06:53:45 +02:00
license Let PoolThreadCache work even if allocation and deallocation Thread are different 2015-05-27 14:35:22 +02:00
microbench [maven-release-plugin] prepare for next development iteration 2016-07-01 07:59:55 +02:00
tarball [maven-release-plugin] prepare for next development iteration 2016-07-01 07:59:55 +02:00
testsuite [maven-release-plugin] prepare for next development iteration 2016-07-01 07:59:55 +02:00
testsuite-osgi [maven-release-plugin] prepare for next development iteration 2016-07-01 07:59:55 +02:00
transport [#5486] Not operate on serial execution assumption when using EventExecutor in the DefaultChannelPipeline. 2016-07-07 14:53:33 +02:00
transport-native-epoll EPOLL Cached ECONNREFUSED Exception 2016-07-06 12:03:13 -07:00
transport-rxtx [maven-release-plugin] prepare for next development iteration 2016-07-01 07:59:55 +02:00
transport-sctp [maven-release-plugin] prepare for next development iteration 2016-07-01 07:59:55 +02:00
transport-udt [maven-release-plugin] prepare for next development iteration 2016-07-01 07:59:55 +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:53:28 +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:18:14 +09:00
LICENSE.txt Relicensed to Apache License v2 2009-08-28 07:15:49 +00:00
NOTICE.txt Let PoolThreadCache work even if allocation and deallocation Thread are different 2015-05-27 14:35:22 +02:00
pom.xml [maven-release-plugin] prepare for next development iteration 2016-07-01 07:59:55 +02:00
README.md Updating Branches to look section to match the current branching structure of the project 2016-03-10 22:09:30 +01:00
run-example.sh Add logLevel property to enable different log levels for the examples. 2014-11-21 10:48:13 +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

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.