Go to file
Trustin Lee 5b87cdc8bd Reduce the perceived time taken to retrieve initialSeedUniquifier
Motivation:

When system is in short of entrophy, the initialization of
ThreadLocalRandom can take at most 3 seconds.  The initialization occurs
when ThreadLocalRandom.current() is invoked first time, which might be
much later than the moment when the application has started.  If we
start the initialization of ThreadLocalRandom as early as possible, we
can reduce the perceived time taken for the retrieval.

Modification:

Begin the initialization of ThreadLocalRandom in InternalLoggerFactory,
potentially one of the firstly initialized class in a Netty application.

Make DefaultChannelId retrieve the current process ID before retrieving
the current machine ID, because retrieval of a machine ID is more likely
to use ThreadLocalRandom.current().

Use a dummy channel ID for EmbeddedChannel, which prevents many unit
tests from creating a ThreadLocalRandom instance.

Result:

We gain extra 100ms at minimum for initialSeedUniquifier generation.  If
an application has its own initialization that takes long enough time
and generates good amount of entrophy, it is very likely that we will
gain a lot more.
2014-07-04 16:04:48 +09:00
all Add MQTT protocol codec 2014-06-21 16:52:10 +09:00
buffer Fix the build timeout when 'leak' profile is active 2014-07-03 17:55:10 +09:00
codec Make JsonObjectDecoder discard everything after stream corruption 2014-07-04 11:16:00 +09:00
codec-dns Fix most inspector warnings 2014-07-02 19:55:07 +09:00
codec-haproxy Fix test failures due to incorrect validation 2014-06-21 17:11:35 +09:00
codec-http Fix most inspector warnings 2014-07-02 19:55:07 +09:00
codec-memcache Fix most inspector warnings 2014-07-02 19:55:07 +09:00
codec-mqtt Mqtt -> MQTT 2014-06-21 17:14:41 +09:00
codec-socks Fix most inspector warnings 2014-07-02 19:55:07 +09:00
codec-stomp Fix most inspector warnings 2014-07-02 19:55:07 +09:00
common Reduce the perceived time taken to retrieve initialSeedUniquifier 2014-07-04 16:04:48 +09:00
example Let OkResponseHandler extend SimpleChannelInboundHandler 2014-07-03 18:14:40 +09:00
handler [#2618] Introduce ChannelPromise.unvoid() and ChannelFuture.isVoid() 2014-07-03 14:17:12 +02: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 Reduce the perceived time taken to retrieve initialSeedUniquifier 2014-07-04 16:04:48 +09:00
transport-native-epoll Fix most inspector warnings 2014-07-02 19:55:07 +09:00
transport-rxtx Fix most inspector warnings 2014-07-02 19:55:07 +09:00
transport-sctp Fix most inspector warnings 2014-07-02 19:55:07 +09:00
transport-udt Fix most inspector warnings 2014-07-02 19:55:07 +09: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 Fix most inspector warnings 2014-07-02 19:55:07 +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

Netty Project

Netty is an asynchronous event-driven network application framework for rapid development of maintainable high performance protocol servers & clients.

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.