andreacavalli/netty5
1
0
Fork 0
Code Issues Pull Requests Projects Releases Wiki Activity
5,850 Commits 27 Branches 234 Tags 84 MiB
Java 99.8%
Shell 0.1%
2d9e0f53a5
Go to file
Norman Maurer 2d9e0f53a5 Better implementation of AttributeMap and also add hasAttr(...). See [#2439] 
Motivation:
The old DefaultAttributeMap impl did more synchronization then needed and also did not expose a efficient way to check if an attribute exists with a specific key.

Modifications:
* Rewrite DefaultAttributeMap to not use IdentityHashMap and synchronization on the map directly. The new impl uses a combination of AtomicReferenceArray and synchronization per chain (linked-list). Also access the first Attribute per bucket can be done without any synchronization at all and just uses atomic operations. This should fit for most use-cases pretty weel.
* Add hasAttr(...) implementation

Result:
It's now possible to check for the existence of a attribute without create one. Synchronization is per linked-list and the first entry can even be added via atomic operation.
2014-05-15 06:47:42 +02:00
all Generate the default JAR to make oss.sonatype.org happy 2014-05-03 17:32:45 +09:00
buffer Fix capacity check bug affecting offheap buffers 2014-05-13 07:25:15 +02:00
codec Use ByteBuf.readSlice(...).retain() to minimize memory copies. 2014-05-10 17:20:53 +02:00
codec-http Adding short-curcuit option for CORS 2014-05-06 12:16:57 +02:00
codec-memcache Synchronized between 4.1 and master (part 3) 2014-04-25 16:17:59 +09:00
codec-socks Correctly handle SocksCmdResponse. Related to #2428 2014-04-30 10:44:17 +02:00
common Better implementation of AttributeMap and also add hasAttr(...). See [#2439] 2014-05-15 06:47:42 +02:00
example Synchronized between 4.1 and master again (part 2) 2014-04-25 15:06:26 +09:00
handler Correctly write pending data after ssl handshake completes. Related to [#2437] 2014-04-30 14:23:18 +02:00
license [#1259] Add optimized queue for SCMP pattern and use it in NIO and native transport 2014-02-27 13:28:37 +01:00
microbench Upgrade JMH to 0.4.1 and make use of @Params. 2014-02-23 16:39:39 +01:00
tarball Update the version to 4.1.0.Alpha1-SNAPSHOT 2014-02-13 18:32:26 -08:00
testsuite Correctly write pending data after ssl handshake completes. Related to [#2437] 2014-04-30 14:23:18 +02:00
transport Better implementation of AttributeMap and also add hasAttr(...). See [#2439] 2014-05-15 06:47:42 +02:00
transport-native-epoll [#2485] Use RecvByteBufAllocator for all allocations related to read from Channel 2014-05-10 15:27:43 +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 Format and partially describe Gitignore 2013-12-10 07:04:38 +01: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 [#1259] Add optimized queue for SCMP pattern and use it in NIO and native transport 2014-02-27 13:28:37 +01:00
pom.xml Fix the life cycle mapping problem with m2e 2014-05-12 21:38:09 +09:00
README.md Synchronized between 4.1 and master 2014-04-25 00:38:02 +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.