Norman Maurer 0d62d4cce1 Ensure we not leave data in the BIO when error happens.
Motivation:

We need to ensure we consume all pending data in the BIO on error to correctly send the close notify for the remote peer.

Modifications:

Correctly force the user to call wrap(...) if there is something left in the BIO.

Result:

close_notify is not lost.
2015-12-17 12:39:51 +09:00
2015-11-24 21:24:22 +01:00
2015-11-24 21:24:22 +01:00
2015-11-24 21:24:22 +01:00
2015-11-24 21:24:22 +01:00
2015-11-24 21:24:22 +01:00
2015-11-24 21:24:22 +01:00
2015-11-24 21:24:22 +01:00
2015-11-24 21:24:22 +01:00
2015-11-24 21:24:22 +01:00
2015-11-24 21:24:22 +01:00
2015-11-24 21:24:22 +01:00
2015-11-24 21:24:22 +01: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
2015-11-24 21:24:22 +01:00
2015-10-27 13:58:06 +01: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.

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