andreacavalli/netty5
1
0
Fork 0
Code Issues Pull Requests Projects Releases Wiki Activity
6,259 Commits 27 Branches 234 Tags 84 MiB
Java 99.8%
Shell 0.1%
c72c71abbb
Go to file
Norman Maurer c72c71abbb [#3662] Fail the connect future on close 
Motivation:

Because of a bug we missed to fail the connect future when doClose() is called. This can lead to a future which is never notified and so may lead to deadlocks in user-programs.

Modifications:

Correctly fail the connect future when doClose() is called and the connection was not established yet.

Result:

Connect future is always notified.
2015-04-27 20:04:34 +02:00
all [maven-release-plugin] prepare for next development iteration 2015-03-31 22:06:30 -04:00
buffer [#3623] CompositeByteBuf.iterator() should return optimized Iterable 2015-04-20 10:45:28 +02:00
codec fix the discardedBytes counting on LineBasedFrameDecoder 2015-04-21 09:25:57 +02:00
codec-http Fix handling of non-auto read for ByteToMessageDecoder and SslHandler 2015-04-20 09:02:47 +02:00
codec-socks [maven-release-plugin] prepare for next development iteration 2015-03-31 22:06:30 -04:00
common [#3680] Enabled SecurityManager results in ClassNotFoundError during io.netty.util.NetUtil initialization 2015-04-27 20:01:51 +02:00
example [#3531] Create SslContext.Builder 2015-04-14 07:27:55 +02:00
handler Fix SslContextBuilder swapping client and server 2015-04-20 17:24:43 -07:00
license Remove license of deque as we not use it anymore 2014-08-04 12:21:33 +02:00
microbench [maven-release-plugin] prepare for next development iteration 2015-03-31 22:06:30 -04:00
tarball [maven-release-plugin] prepare for next development iteration 2015-03-31 22:06:30 -04:00
testsuite Correctly test for non-auto-read correctness in testsuite 2015-04-20 09:02:40 +02:00
testsuite-osgi [maven-release-plugin] prepare for next development iteration 2015-03-31 22:06:30 -04:00
transport [#3662] Fail the connect future on close 2015-04-27 20:04:34 +02:00
transport-native-epoll [#3662] Fail the connect future on close 2015-04-27 20:04:34 +02:00
transport-rxtx [maven-release-plugin] prepare for next development iteration 2015-03-31 22:06:30 -04:00
transport-sctp [maven-release-plugin] prepare for next development iteration 2015-03-31 22:06:30 -04:00
transport-udt Motivation: If there are no readable bytes, it's unnecessary to go through javaChannel().write(). 2015-04-08 09:36:32 +02:00
.fbprefs Updated Find Bugs configuration 2009-03-04 10:33:09 +00:00
.gitignore Add JVM crash logs to .gitignore 2014-05-18 21:37:12 +09: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 Remove license of deque as we not use it anymore 2014-08-04 12:21:33 +02:00
pom.xml Add support for ALPN when using openssl + NPN client mode and support for CipherSuiteFilter 2015-04-10 18:59:58 +02:00
README.md Add a link to the 'native transports' page 2014-07-21 12:54:43 -07: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

The 'master' branch is where the development of the latest major version lives on. The development of all other major versions takes place in each branch whose name is identical to its major version number. For example, the development of 3.x and 4.x resides in the branch '3' and the branch '4' respectively.