andreacavalli/netty5
1
0
Fork 0
Code Issues Pull Requests Projects Releases Wiki Activity
5,927 Commits 27 Branches 234 Tags 84 MiB
Java 99.8%
Shell 0.1%
3f3e66c31a
Go to file
Norman Maurer 3f3e66c31a Allow to use ChannelOutboundBuffer without AbstractChannel 
Motivation:

We expose ChannelOutboundBuffer in Channel.Unsafe but it is not possible
to create a new ChannelOutboundBuffer without an AbstractChannel.  This
makes it impossible to write a Channel implementation that does not
extend AbstractChannel.

Modifications:

- Change ChannelOutboundBuffer to take a Channel as constructor argument.
- Add javadocs

Result:

ChannelOutboundBuffer can be used with a Channel implemention that does
not extend AbstractChannel.
2014-08-04 12:44:38 -07:00
all [maven-release-plugin] prepare for next development iteration 2014-06-30 14:31:08 +02:00
buffer Remove duplicate range check in AbstractByteBuf.skipBytes() 2014-07-29 15:58:38 -07:00
codec [#2705] Call fireChannelReadComplete() if channelActive(...) decodes messages in ReplayingDecoder / ByteToMessageDecoder 2014-07-24 14:33:56 +02:00
codec-http Use our own URL shortener wherever possible 2014-07-31 17:05:54 -07:00
codec-socks Fix most inspector warnings 2014-07-02 20:21:30 +09:00
common More brief somaxconn logging 2014-08-04 10:25:11 -07:00
example Move generic code to HttpOrSpdyChooser to simplify implementations 2014-07-07 09:34:33 +02:00
handler Clean-up d9cccccbb3 2014-08-04 10:53:39 -07:00
license Remove license of deque as we not use it anymore 2014-08-04 12:21:33 +02:00
microbench [maven-release-plugin] prepare for next development iteration 2014-06-30 14:31:08 +02:00
tarball [maven-release-plugin] prepare for next development iteration 2014-06-30 14:31:08 +02:00
testsuite [#2647] Respect IOV_MAX when call writev in native transport 2014-07-09 13:32:43 +02:00
transport Allow to use ChannelOutboundBuffer without AbstractChannel 2014-08-04 12:44:38 -07:00
transport-native-epoll Fix a stall write in EpollSocketChannel 2014-08-01 16:58:12 -07:00
transport-rxtx Fix most inspector warnings 2014-07-02 20:21:30 +09:00
transport-sctp [#2644] Correctly release buffer when exception happens during send DatagramPacket or SctpMessage 2014-07-08 20:15:33 +02:00
transport-udt Fix most inspector warnings 2014-07-02 20:21:30 +09: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:37:12 +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:18:14 +09:00
LICENSE.txt Relicensed to Apache License v2 2009-08-28 07:15:49 +00:00
NOTICE.txt Remove license of deque as we not use it anymore 2014-08-04 12:21:33 +02:00
pom.xml Add missing m2eclipse life cycle mapping 2014-07-06 16:53:53 +09:00
README.md Add a link to the 'native transports' page 2014-07-21 12:54:43 -07:00
run-example.sh Use a forked exec-maven-plugin instead of maven-antrun-plugin 2014-05-23 20:06:12 +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 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.