Go to file
Trustin Lee cbd8817905 Remove MessageList from public API and change ChannelInbound/OutboundHandler accordingly
I must admit MesageList was pain in the ass.  Instead of forcing a
handler always loop over the list of messages, this commit splits
messageReceived(ctx, list) into two event handlers:

- messageReceived(ctx, msg)
- mmessageReceivedLast(ctx)

When Netty reads one or more messages, messageReceived(ctx, msg) event
is triggered for each message.  Once the current read operation is
finished, messageReceivedLast() is triggered to tell the handler that
the last messageReceived() was the last message in the current batch.

Similarly, for outbound, write(ctx, list) has been split into two:

- write(ctx, msg)
- flush(ctx, promise)

Instead of writing a list of message with a promise, a user is now
supposed to call write(msg) multiple times and then call flush() to
actually flush the buffered messages.

Please note that write() doesn't have a promise with it.  You must call
flush() to get notified on completion. (or you can use writeAndFlush())

Other changes:

- Because MessageList is completely hidden, codec framework uses
  List<Object> instead of MessageList as an output parameter.
2013-07-09 23:51:48 +09:00
all [maven-release-plugin] prepare for next development iteration 2013-07-02 11:41:18 +02:00
buffer Make ByteBuf an abstract class rather than an interface 2013-07-08 14:59:52 +09:00
codec Remove MessageList from public API and change ChannelInbound/OutboundHandler accordingly 2013-07-09 23:51:48 +09:00
codec-http Remove MessageList from public API and change ChannelInbound/OutboundHandler accordingly 2013-07-09 23:51:48 +09:00
codec-socks Remove MessageList from public API and change ChannelInbound/OutboundHandler accordingly 2013-07-09 23:51:48 +09:00
common [#1535] Remove Channel.id() and so fix the possible leakage of the previous used Channel id map 2013-07-08 14:07:18 +02:00
example Remove MessageList from public API and change ChannelInbound/OutboundHandler accordingly 2013-07-09 23:51:48 +09:00
handler Remove MessageList from public API and change ChannelInbound/OutboundHandler accordingly 2013-07-09 23:51:48 +09:00
license Add back jzlib license file and notice 2013-02-21 14:00:59 -08:00
microbench [maven-release-plugin] prepare for next development iteration 2013-07-02 11:41:18 +02:00
tarball [maven-release-plugin] prepare for next development iteration 2013-07-02 11:41:18 +02:00
testsuite Remove MessageList from public API and change ChannelInbound/OutboundHandler accordingly 2013-07-09 23:51:48 +09:00
testsuite-osgi [maven-release-plugin] prepare for next development iteration 2013-07-02 11:41:18 +02:00
transport Remove MessageList from public API and change ChannelInbound/OutboundHandler accordingly 2013-07-09 23:51:48 +09:00
transport-rxtx Remove Channel.id completely / Use 64-bit hashCode internally to reduce the chance of collision in compareTo() 2013-07-09 14:49:06 +09:00
transport-sctp Remove MessageList from public API and change ChannelInbound/OutboundHandler accordingly 2013-07-09 23:51:48 +09:00
transport-udt Remove MessageList from public API and change ChannelInbound/OutboundHandler accordingly 2013-07-09 23:51:48 +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 ignore .idea/ folder 2012-01-16 16:01:00 +08:00
.travis.yml Travis CI branch whitelisting 2013-03-11 09:55:43 +09:00
LICENSE.txt Relicensed to Apache License v2 2009-08-28 07:15:49 +00:00
NOTICE.txt Add back jzlib license file and notice 2013-02-21 14:00:59 -08:00
pom.xml [maven-release-plugin] prepare for next development iteration 2013-07-02 11:41:18 +02:00
README.md Fix broken url 2013-02-26 16:29:24 -08: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