5112cec5fa
Related: #2983 Motivation: It is a well known idiom to write an empty buffer and add a listener to its future to close a channel when the last byte has been written out: ChannelFuture f = channel.writeAndFlush(Unpooled.EMPTY_BUFFER); f.addListener(ChannelFutureListener.CLOSE); When HttpObjectEncoder is in the pipeline, this still works, but it silently raises an IllegalStateException, because HttpObjectEncoder does not allow writing a ByteBuf when it is expecting an HttpMessage. Modifications: - Handle an empty ByteBuf specially in HttpObjectEncoder, so that writing an empty buffer does not fail even if the pipeline contains an HttpObjectEncoder - Add a test Result: An exception is not triggered anymore by HttpObjectEncoder, when a user attempts to write an empty buffer. |
||
|---|---|---|
| all | ||
| buffer | ||
| codec | ||
| codec-http | ||
| codec-socks | ||
| common | ||
| example | ||
| handler | ||
| license | ||
| microbench | ||
| tarball | ||
| testsuite | ||
| transport | ||
| transport-native-epoll | ||
| transport-rxtx | ||
| transport-sctp | ||
| transport-udt | ||
| .fbprefs | ||
| .gitignore | ||
| .travis.yml | ||
| CONTRIBUTING.md | ||
| LICENSE.txt | ||
| NOTICE.txt | ||
| pom.xml | ||
| README.md | ||
| run-example.sh | ||
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:
- Latest stable Oracle JDK 7
- Latest stable Apache Maven
- If you are on Linux, you need additional development packages installed on your system, because you'll build the native transport.
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.