andreacavalli/netty5
1
0
Fork 0
Code Issues Pull Requests Projects Releases Wiki Activity
6,843 Commits 27 Branches 234 Tags 84 MiB
Java 99.8%
Shell 0.1%
7fb2dd7383
Go to file
Norman Maurer 7fb2dd7383 Allow to inject RejectedExecutionHandler for different EventLoops and EventExecutors 
Motiviation:

Sometimes it is useful to allow to specify a custom strategy to handle rejected tasks. For example if someone tries to add tasks from outside the eventloop it may make sense to try to backoff and retries and so give the executor time to recover.

Modification:

Add RejectedEventExecutor interface and implementations and allow to inject it.

Result:

More flexible handling of executor overload.
2016-06-24 17:57:34 +02:00
all [maven-release-plugin] prepare for next development iteration 2016-06-07 20:00:14 +02:00
buffer Pluggable resource leak detector 2016-06-20 11:17:07 +02:00
codec Use shaded dependency on JCTools instead of copy and paste 2016-06-10 13:53:28 +02:00
codec-haproxy [maven-release-plugin] prepare for next development iteration 2016-06-07 20:00:14 +02:00
codec-http Set some StackTraceElement on pre-instantiated static exceptions 2016-06-20 11:37:19 +02:00
codec-socks [maven-release-plugin] prepare for next development iteration 2016-06-07 20:00:14 +02:00
common Allow to inject RejectedExecutionHandler for different EventLoops and EventExecutors 2016-06-24 17:57:34 +02:00
example Ensure examples are runnable in the ide 2016-06-20 07:11:43 +02:00
handler Correctly implement SSLSession.getLastAccessedTime() for OpenSSLEngine 2016-06-23 11:31:12 +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-06-07 20:00:14 +02:00
tarball [maven-release-plugin] prepare for next development iteration 2016-06-07 20:00:14 +02:00
testsuite [maven-release-plugin] prepare for next development iteration 2016-06-07 20:00:14 +02:00
testsuite-osgi [maven-release-plugin] prepare for next development iteration 2016-06-07 20:00:14 +02:00
transport Allow to inject RejectedExecutionHandler for different EventLoops and EventExecutors 2016-06-24 17:57:34 +02:00
transport-native-epoll Allow to inject RejectedExecutionHandler for different EventLoops and EventExecutors 2016-06-24 17:57:34 +02:00
transport-rxtx Use shaded dependency on JCTools instead of copy and paste 2016-06-10 13:53:28 +02:00
transport-sctp Use shaded dependency on JCTools instead of copy and paste 2016-06-10 13:53:28 +02:00
transport-udt [maven-release-plugin] prepare for next development iteration 2016-06-07 20:00:14 +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 Correctly handle user home directory with spaces when construct javaagent argument 2016-06-17 06:34:23 +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.