andreacavalli/netty5
1
0
Fork 0
Code Issues Pull Requests Projects Releases Wiki Activity
5,901 Commits 27 Branches 234 Tags 84 MiB
Java 99.8%
Shell 0.1%
a79b69adf5
Go to file
Norman Maurer a79b69adf5 ChannelFlushPromiseNotifier should allow long value for pendingDataSize 
Motivation:
At the moment ChannelFlushPromiseNotifier.add(....) takes an int value for pendingDataSize, which may be too small as a user may need to use a long. This can for example be useful when a user writes a FileRegion etc. Beside this the notify* method names are kind of missleading as these should not contain *Future* because it is about ChannelPromises.

Modification:
Add a new add(...) method that takes a long for pendingDataSize and @deprecated the old method. Beside this also @deprecated all *Future* methods and add methods that have *Promise* in the method name to better reflect usage.

Result:
ChannelFlushPromiseNotifier can be used with bigger data.
2014-06-03 17:34:53 +02:00
all Use a forked exec-maven-plugin instead of maven-antrun-plugin 2014-05-23 20:06:04 +09:00
buffer Use Java 5 foreach for arrays for brevity at no cost 2014-06-02 18:25:25 +09:00
codec [#2525] Use VoidChannelPromise in MessageToMessageEncoder when possible 2014-06-01 19:26:20 +02:00
codec-http codec-http: Document the semantics of HttpResponseStatus equality and comparison 2014-05-30 07:52:20 +02:00
codec-memcache Synchronized between 4.1 and master (part 3) 2014-04-25 16:17:59 +09:00
codec-socks Clean up the examples 2014-05-23 17:13:09 +09:00
common Add awaitInactivity() to GlobalEventExecutor and ThreadDeathWatcher 2014-06-02 19:28:00 +09:00
example OkResponseHandler should return a FullHttpResponse. 2014-06-03 09:44:32 +02:00
handler [#2494] Fix data curruption by ChannelTrafficShapingHandler 2014-06-03 08:38:05 +02:00
license Preparation for porting OpenSSL support in 3.10 2014-05-17 20:01:30 +09:00
microbench More realistic ByteBuf allocation benchmark 2014-05-29 19:51:05 +09:00
tarball Update the version to 4.1.0.Alpha1-SNAPSHOT 2014-02-13 18:32:26 -08:00
testsuite Add an OpenSslEngine and the universal API for enabling SSL 2014-05-18 02:54:06 +09:00
transport ChannelFlushPromiseNotifier should allow long value for pendingDataSize 2014-06-03 17:34:53 +02:00
transport-native-epoll Add an OpenSslEngine and the universal API for enabling SSL 2014-05-18 02:54:06 +09: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 Add JVM crash logs to .gitignore 2014-05-18 21:36:54 +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:13:58 +09:00
LICENSE.txt Relicensed to Apache License v2 2009-08-28 07:15:49 +00:00
NOTICE.txt Preparation for porting OpenSSL support in 3.10 2014-05-17 20:01:30 +09:00
pom.xml Upgrade to netty-tcnative 1.1.30.Fork2 to support Windows 2014-05-28 10:56:15 +09:00
README.md Synchronized between 4.1 and master 2014-04-25 00:38:02 +09:00
run-example.sh Use a forked exec-maven-plugin instead of maven-antrun-plugin 2014-05-23 20:06:04 +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.