Go to file
Trustin Lee cea3b6b2ab Clean up HTTP/2 integration tests
Related pull request: #2481 written by @nmittler

Motivation:

Some tests were still sending requests from the test thread rather than
from the event loop.

Modifications:

- Modified the roundtrip tests to use a new utility Http2TestUtil to
  perform the write operations in the event loop thread.
- Modified the Http2Client under examples to write all requests in the
  event loop thread.
- Added HttpPrefaceHandler and its test which were missing.
- Fixed various inspector warnings

Result:

Tests and examples now send requests in the correct thread context.
2014-07-02 16:58:24 +09:00
all Add MQTT protocol codec 2014-06-21 16:51:37 +09:00
buffer [#2622] Correctly check reference count before try to work on the underlying memory 2014-06-30 07:14:37 +02:00
codec fix example missing break statement in ReplayingDecoder 2014-06-28 21:41:49 +02:00
codec-dns DNS codec for Netty which is based on the work of [#1622]. 2014-06-10 09:47:25 +02:00
codec-haproxy Fix test failures due to incorrect validation 2014-06-21 17:11:08 +09:00
codec-http Fix compile error 2014-06-28 22:27:15 +02:00
codec-http2 Clean up HTTP/2 integration tests 2014-07-02 16:58:24 +09:00
codec-memcache Fix potential buffer leak in AbstractBinaryMemcacheDecoder 2014-06-24 16:24:48 +09:00
codec-mqtt Mqtt -> MQTT 2014-06-21 17:14:20 +09:00
codec-socks Hide SocksMessage.encodeAsByteBuf() from public API 2014-06-24 16:43:58 +09:00
codec-stomp Introduce TextHeaders and AsciiString 2014-06-14 17:14:30 +09:00
common Correctly return from selector loop one a scheduled task is ready for processing 2014-07-02 09:10:49 +02:00
example The temporary variable is no longer used in an attempt to accumulate data over onDataRead method class 2014-06-27 06:39:35 +02:00
handler Refactor FastThreadLocal to simplify TLV management 2014-06-19 21:17:46 +09:00
license Implement a Bzip2Decoder 2014-06-24 14:49:49 +09:00
microbench Fix the inconsistencies between performance tests in ByteBufAllocatorBenchmark 2014-06-21 13:27:28 +09:00
tarball [maven-release-plugin] prepare for next development iteration 2013-12-22 22:06:15 +09:00
testsuite Remove 'get' prefix from all HTTP/SPDY messages 2014-06-24 18:41:27 +09:00
transport Correctly return from selector loop one a scheduled task is ready for processing 2014-07-02 09:10:49 +02:00
transport-native-epoll [#2558] Define SO_REUSEPORT if not defined 2014-07-02 09:40:36 +02:00
transport-rxtx Resurrect channel deregistration and constructor changes 2014-04-24 20:54:50 +09:00
transport-sctp Synchronized between 4.1 and master again (part 2) 2014-04-25 15:07:12 +09:00
transport-udt Synchronized between 4.1 and master again (part 2) 2014-04-25 15:07:12 +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:34:51 +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:17: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:49:49 +09:00
pom.xml Upgrade JACOCO to the latest version 2014-06-27 17:24:05 +09:00
README.md Synchronized between 4.1 and master (part 3) 2014-04-25 16:17:16 +09:00
run-example.sh Overall refactoring of the STOMP codec 2014-06-04 17:09:11 +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.