andreacavalli/netty5
1
0
Fork 0
Code Issues Pull Requests Projects Releases Wiki Activity
8,352 Commits 27 Branches 234 Tags 84 MiB
Java 99.8%
Shell 0.1%
f8b495b2f2
Go to file
Norman Maurer f8b495b2f2 Correctly support SO_TIMEOUT for OioDatagramChannel 
Motivation:

We need to support SO_TIMEOUT for the OioDatagramChannel but we miss this atm as we not have special handling for it in the DatagramChannelConfig impl that we use. Because of this the following log lines showed up when running the testsuite:

20:31:26.299 [main] WARN  io.netty.bootstrap.Bootstrap - Unknown channel option 'SO_TIMEOUT' for channel '[id: 0x7cb9183c]'

Modifications:

- Add OioDatagramChannelConfig and impl
- Correctly set SO_TIMEOUT in testsuite

Result:

Support SO_TIMEOUT for OioDatagramChannel and so faster execution of datagram related tests in the testsuite
2017-08-08 09:08:33 +02:00
.github Use GitHub Issue/PR Template Feature 2016-12-07 11:40:26 -08:00
all [maven-release-plugin] prepare for next development iteration 2017-08-02 12:55:10 +00:00
bom [maven-release-plugin] prepare for next development iteration 2017-08-02 12:55:10 +00:00
buffer [maven-release-plugin] prepare for next development iteration 2017-08-02 12:55:10 +00:00
codec Handle partially decoded elements while streaming Json array 2017-08-08 08:48:01 +02:00
codec-dns [maven-release-plugin] prepare for next development iteration 2017-08-02 12:55:10 +00:00
codec-haproxy [maven-release-plugin] prepare for next development iteration 2017-08-02 12:55:10 +00:00
codec-http Add testcases to prove HttpResponseEncoder correctly handles empty content 2017-08-07 07:25:33 +02:00
codec-http2 Fix incorrect javadocs in Http2RemoteFlowController 2017-08-08 07:47:18 +02:00
codec-memcache [maven-release-plugin] prepare for next development iteration 2017-08-02 12:55:10 +00:00
codec-mqtt [maven-release-plugin] prepare for next development iteration 2017-08-02 12:55:10 +00:00
codec-redis [maven-release-plugin] prepare for next development iteration 2017-08-02 12:55:10 +00:00
codec-smtp [maven-release-plugin] prepare for next development iteration 2017-08-02 12:55:10 +00:00
codec-socks [maven-release-plugin] prepare for next development iteration 2017-08-02 12:55:10 +00:00
codec-stomp [maven-release-plugin] prepare for next development iteration 2017-08-02 12:55:10 +00:00
codec-xml [maven-release-plugin] prepare for next development iteration 2017-08-02 12:55:10 +00:00
common Remove code-duplication from NativeLibraryLoader 2017-08-08 09:06:41 +02:00
dev-tools [maven-release-plugin] prepare for next development iteration 2017-08-02 12:55:10 +00:00
example [maven-release-plugin] prepare for next development iteration 2017-08-02 12:55:10 +00:00
handler Only call ctx.fireChannelReadComplete() if ByteToMessageDecoder decoded at least one message. 2017-08-04 10:54:56 +02:00
handler-proxy [maven-release-plugin] prepare for next development iteration 2017-08-02 12:55:10 +00:00
license Remove reference to akka code and ArrayDeque which is not part of netty anymore 2017-03-07 21:30:51 +01:00
microbench [maven-release-plugin] prepare for next development iteration 2017-08-02 12:55:10 +00:00
resolver [maven-release-plugin] prepare for next development iteration 2017-08-02 12:55:10 +00:00
resolver-dns [maven-release-plugin] prepare for next development iteration 2017-08-02 12:55:10 +00:00
tarball [maven-release-plugin] prepare for next development iteration 2017-08-02 12:55:10 +00:00
testsuite Correctly support SO_TIMEOUT for OioDatagramChannel 2017-08-08 09:08:33 +02:00
testsuite-autobahn [maven-release-plugin] prepare for next development iteration 2017-08-02 12:55:10 +00:00
testsuite-osgi [maven-release-plugin] prepare for next development iteration 2017-08-02 12:55:10 +00:00
transport Correctly support SO_TIMEOUT for OioDatagramChannel 2017-08-08 09:08:33 +02:00
transport-native-epoll Shutting down the outbound side of the channel should not accept future writes 2017-08-04 10:59:57 -07:00
transport-native-kqueue Shutting down the outbound side of the channel should not accept future writes 2017-08-04 10:59:57 -07:00
transport-native-unix-common Correctly handle connect/disconnect in EpollDatagramChannel / KQueueDatagramChannel 2017-08-04 09:22:53 +02:00
transport-native-unix-common-tests [maven-release-plugin] prepare for next development iteration 2017-08-02 12:55:10 +00:00
transport-rxtx [maven-release-plugin] prepare for next development iteration 2017-08-02 12:55:10 +00:00
transport-sctp [maven-release-plugin] prepare for next development iteration 2017-08-02 12:55:10 +00:00
transport-udt [maven-release-plugin] prepare for next development iteration 2017-08-02 12:55:10 +00: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:19:45 +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:13:58 +09:00
LICENSE.txt Relicensed to Apache License v2 2009-08-28 07:15:49 +00:00
NOTICE.txt Remove reference to akka code and ArrayDeque which is not part of netty anymore 2017-03-07 21:30:51 +01:00
pom.xml asm 6.0_BETA was released so we should use it when building on java9 2017-08-05 08:16:50 +02:00
README.md Updating Branches to look section to match the current branching structure of the project 2016-03-10 22:08:01 +01:00
run-example.sh Add UptimeServer and adjust UptimeClient's code style. 2017-04-28 07:41:07 +02: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.