andreacavalli/netty5
1
0
Fork 0
Code Issues Pull Requests Projects Releases Wiki Activity
5,971 Commits 27 Branches 234 Tags 84 MiB
Java 99.8%
Shell 0.1%
b0e5c9be00
Go to file
Norman Maurer b0e5c9be00 [#2605] Use SO_REUSEADDR on EpollServerSocketChannel to match defaults of java.nio.ServerSocketChannel impl 
Motivation:

When using openjdk and oracle jdk's nio (while using the nio transport) the ServerSocketChannel uses SO_REUSEADDR by default. Our native transport should do the same to make it easier to switch between the different implementations and get the expected result.

Modification:

Change EpollServerSocketChannelConfig to set SO_REUSEADDR on the created socket.

Result:

SO_REUSEADDR is used by default on servers.
2014-06-26 11:57:40 +02:00
all Add MQTT protocol codec 2014-06-21 16:52:10 +09:00
buffer Optimize PoolChunk 2014-06-26 17:06:10 +09:00
codec Fix incorrect bytesBefore/indexOf() in ReplayingDecoderBuffer 2014-06-26 18:56:33 +09:00
codec-dns DNS codec for Netty which is based on the work of [#1622]. 2014-06-10 09:57:06 +02:00
codec-haproxy Fix test failures due to incorrect validation 2014-06-21 17:11:35 +09:00
codec-http Fix integer overflow in HttpObjectEncoder when handling chunked encoding and FileRegion > Integer.MAX_VALUE 2014-06-24 12:03:48 +02:00
codec-memcache Fix potential buffer leak in AbstractBinaryMemcacheDecoder 2014-06-24 16:25:40 +09:00
codec-mqtt Mqtt -> MQTT 2014-06-21 17:14:41 +09:00
codec-socks Deprecate SocksMessage.encodeAsByteBuf() 2014-06-24 16:40:44 +09:00
codec-stomp Introduce TextHeaders and AsciiString 2014-06-14 15:36:19 +09:00
common [#2599] Not use sun.nio.ch.DirectBuffer as it not exists on android 2014-06-25 15:07:02 +02:00
example Remove 'get' prefix from all HTTP/SPDY messages 2014-06-24 18:03:33 +09:00
handler Refactor FastThreadLocal to simplify TLV management 2014-06-19 21:13:55 +09:00
license Implement a Bzip2Decoder 2014-06-24 14:50:09 +09:00
microbench Fix the inconsistencies between performance tests in ByteBufAllocatorBenchmark 2014-06-21 13:28:02 +09:00
tarball Update the version to 4.1.0.Alpha1-SNAPSHOT 2014-02-13 18:32:26 -08:00
testsuite Remove 'get' prefix from all HTTP/SPDY messages 2014-06-24 18:03:33 +09:00
transport Fix a typo in comment 2014-06-24 11:01:35 +02:00
transport-native-epoll [#2605] Use SO_REUSEADDR on EpollServerSocketChannel to match defaults of java.nio.ServerSocketChannel impl 2014-06-26 11:57:40 +02:00
transport-rxtx Synchronized between 4.1 and master again (part 2) 2014-04-25 15:06:26 +09:00
transport-sctp Synchronized between 4.1 and master again (part 2) 2014-04-25 15:06:26 +09:00
transport-udt Synchronized between 4.1 and master again (part 2) 2014-04-25 15:06:26 +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 Add JVM crash logs to .gitignore 2014-05-18 21:36:54 +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:13:58 +09:00
LICENSE.txt Relicensed to Apache License v2 2009-08-28 07:15:49 +00:00
NOTICE.txt Implement a Bzip2Decoder 2014-06-24 14:50:09 +09:00
pom.xml Implement a Bzip2Decoder 2014-06-24 14:50:09 +09:00
README.md Synchronized between 4.1 and master 2014-04-25 00:38:02 +09:00
run-example.sh Overall refactoring of the STOMP codec 2014-06-04 17:09:42 +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.