da9ecadfc0
- Added ChannelBufferHolders.(inbound|outbound)BypassBuffer() - The holder returned by these methods returns the next handler's buffer. When a handler's new(Inbound|Outbound)Buffer returns a bypass holder, your inboundBufferUpdated() and flush() implementation should check if the buffer is a bypass and should not modify the content of the buffer. - Channel(Inbound|Outbound)?HandlerAdapter is now abstract. - A user has to specify the exact inbound/outbound buffer type - It's because there's no way to determine the best buffer type - Implemented LoggingHandler using the new API. - It doesn't dump received or sent messages yet. - Fixed a bug where DefaultUnsafe.close() does not trigger deregister() - Fixed a bug where NioSocketChannel.isActive() does not return false when closed |
||
---|---|---|
all | ||
buffer | ||
codec | ||
codec-http | ||
common | ||
example | ||
handler | ||
license | ||
testsuite | ||
transport | ||
transport-http | ||
transport-rxtx | ||
transport-sctp | ||
.fbfilter.xml | ||
.fbprefs | ||
.gitignore | ||
LICENSE.txt | ||
NOTICE.txt | ||
pom.xml | ||
README.md |
#The Netty Project
Netty is an asynchronous event-driven network application framework for rapid development of maintainable high performance protocol servers & clients.
Links
-
Web Site: http://netty.io/
-
Docs: http://netty.io/docs/
-
Blog: http://netty.io/blog/
-
Twitter: @netty_project
Getting Netty
-
Download Page: http://netty.io/downloads/
-
Maven Repository:
<dependencies>
...
<dependency>
<groupId>io.netty</groupId>
<artifactId>netty</artifactId>
<version>X.Y.Z.Q</version>
<scope>compile</scope>
</dependency>
...
</dependencies>
Developer Information
-
Netty is setup to build using Maven
-
You need JDK 7 to build Netty. Netty will run with JDK 5 (v3.x) and JDK 6 (v4).
-
master branch contains code for Netty v4
-
3.2 branch contains code for Netty v3.X