andreacavalli/netty5
1
0
Fork 0
Code Issues Pull Requests Projects Releases Wiki Activity
5,934 Commits 27 Branches 234 Tags 84 MiB
Java 99.8%
Shell 0.1%
376f4b2516
Go to file
nmittler 376f4b2516 Adding int-to-object map implementation. 
Motivation:

Maps with integer keys are used in several places (HTTP/2 code, for
example). To reduce the memory footprint of these structures, we need a
specialized map class that uses ints as keys.

Modifications:

Added IntObjectHashMap, which is uses open addressing and double hashing
for collision resolution.

Result:

A new int-based map class that can be shared across Netty.
2014-06-16 10:32:16 +02:00
all Initial STOMP protocol work from @sskachkov 2014-06-04 17:09:11 +09:00
buffer Introduce FastThreadLocal which uses an EnumMap and a predefined fixed set of possible thread locals 2014-06-13 11:02:16 +02:00
codec [#2572] Correctly calculate length of output buffer before inflate to fix IndexOutOfBoundException 2014-06-16 10:20:39 +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-http Introduce TextHeaders and AsciiString 2014-06-14 17:14:30 +09:00
codec-http2 Addings helper methods to HTTP/2 handler 2014-06-12 20:52:55 +02:00
codec-memcache Introduce MessageAggregator and DecoderResultProvider 2014-06-05 16:39:59 +09:00
codec-socks Clean up the examples 2014-05-23 16:58:47 +09:00
codec-stomp Introduce TextHeaders and AsciiString 2014-06-14 17:14:30 +09:00
common Adding int-to-object map implementation. 2014-06-16 10:32:16 +02:00
example Introduce TextHeaders and AsciiString 2014-06-14 17:14:30 +09:00
handler Introduce FastThreadLocal which uses an EnumMap and a predefined fixed set of possible thread locals 2014-06-13 11:02:16 +02:00
license Introduce TextHeaders and AsciiString 2014-06-14 17:14:30 +09:00
microbench Introduce FastThreadLocal which uses an EnumMap and a predefined fixed set of possible thread locals 2014-06-13 11:02:16 +02:00
tarball [maven-release-plugin] prepare for next development iteration 2013-12-22 22:06:15 +09:00
testsuite Introduce TextHeaders and AsciiString 2014-06-14 17:14:30 +09:00
transport Introduce FastThreadLocal which uses an EnumMap and a predefined fixed set of possible thread locals 2014-06-13 11:02:16 +02:00
transport-native-epoll Add an OpenSslEngine and the universal API for enabling SSL 2014-05-18 02:33:26 +09: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 Introduce TextHeaders and AsciiString 2014-06-14 17:14:30 +09:00
pom.xml export sun security packages as optional 2014-06-15 21:01:20 +02: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

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.