Norman Maurer cb2246ee07 [#2680] ChannelOutboundBuffer.nioBuffers() should always return non-null array as stated in javadocs
Motivation:

At the moment ChannelOutboundBuffer.nioBuffers() returns null if something is contained in the ChannelOutboundBuffer which is not a ByteBuf. This is a problem for two reasons:
 1 - In the javadocs we state that it will never return null
 2 - We may do a not optimal write as there may be things that could be written via gathering writes

Modifications:

Change ChannelOutboundBuffer.nioBuffers() to never return null but have it contain all ByteBuffer that were found before the non ByteBuf. This way we can do a gathering write and also conform to the javadocs.

Result:

Better speed and also correct implementation in terms of the api.
2014-07-20 19:13:48 +02:00
2014-07-20 09:29:33 +02:00
2014-07-20 09:34:31 +02:00
2014-07-20 12:56:21 +02:00
2014-07-02 20:21:30 +09:00
2014-07-20 12:56:21 +02:00
2014-07-20 12:56:21 +02:00
2014-07-02 20:21:30 +09:00
2009-03-04 10:33:09 +00:00
2014-05-18 21:37:12 +09:00
2013-03-11 09:55:43 +09:00
2009-08-28 07:15:49 +00:00
2014-01-16 14:38:36 +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 major versions takes place in each branch whose name is identical to its major version number. For example, the development of 3.x and 4.x resides in the branch '3' and the branch '4' respectively.

Description
No description provided
Readme 84 MiB
Languages
Java 99.8%
Shell 0.1%