andreacavalli/netty5
1
0
Fork 0
Code Issues Pull Requests Projects Releases Wiki Activity
5,803 Commits 27 Branches 234 Tags 84 MiB
Java 99.8%
Shell 0.1%
b88c7d6f9a
Go to file
Jens Reimann b88c7d6f9a Mark sun.nio.ch as optional 
Motivation:

If sun.nio.ch is not optional this will cause troubles in the
OSGi world. The package is not exposed by default in OSGi, so
actually the whole netty framework cannot be used directly.

There are workarounds, but workarounds are ugly. Especially since
the use of sun.nio.ch is optional. So the requirement on the
package should be optional as well.

Modifications:

Make the import of sun.nio.ch optional.

Result:

If the package cannot be imported it will behave as if the package
sun.nio.ch is not present (like with other JVMs). If the package is
exposed in OSGi (e.g. bootclassloader delegation, extension fragment)
it will be used.
2014-04-23 10:37:39 +02:00
all Ensure native transport is included in all and tarball 2014-02-17 22:46:33 +01:00
buffer Fix error that causes (up to) double memory usage 2014-04-15 06:57:19 +02:00
codec Fix chunk type for stream identifier 2014-04-19 21:06:46 +02:00
codec-http [#2401] Improve documentation of HttpObjectAggregator 2014-04-17 15:42:47 +02:00
codec-http2 HTTP2 server should not send preface string 2014-04-17 21:51:34 +02:00
codec-memcache [codec-memcache] Simplify object hierachy and remove Headers. 2014-03-04 13:04:44 +01:00
codec-socks Fix an inspector warning 2014-02-06 15:03:03 -08:00
common Stop ThreadLocalRandom's initial seed generation immediately on interruption 2014-04-20 17:55:38 +09:00
example HTTP2 server should not send preface string 2014-04-17 21:51:34 +02:00
handler Feed only a single SSL record to SSLEngine.unwrap() 2014-04-20 17:55:38 +09:00
license [#1259] Add optimized queue for SCMP pattern and use it in NIO and native transport 2014-02-27 13:56:15 +01:00
microbench Upgrade JMH to 0.4.1 and make use of @Params. 2014-02-23 16:39:15 +01:00
tarball [maven-release-plugin] prepare for next development iteration 2013-12-22 22:06:15 +09:00
testsuite [#2375] [#2404] Fix bug in respecting ChannelConfig.setAutoRead(false) and also fix Channel.read() for OIO 2014-04-17 08:19:20 +02:00
transport Make NioSocketChannelTest more bullet-proof 2014-04-23 10:05:27 +02:00
transport-native-epoll [#2414] Fix IllegalStateException when try to configure AbstractEpollChannel once it is deregistered 2014-04-22 10:18:27 +02:00
transport-rxtx Apply receive timeout to commPort when using RxtxChannel. Part of [#1390] 2014-02-23 16:35:35 +01:00
transport-sctp [#2375] [#2404] Fix bug in respecting ChannelConfig.setAutoRead(false) and also fix Channel.read() for OIO 2014-04-17 08:19:20 +02:00
transport-udt Enable a user specify an arbitrary information with ReferenceCounted.touch() 2014-01-29 11:44:59 +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 Format and partially describe Gitignore 2013-12-10 07:03:43 +01: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:17:58 +09:00
LICENSE.txt Relicensed to Apache License v2 2009-08-28 07:15:49 +00:00
NOTICE.txt [#1259] Add optimized queue for SCMP pattern and use it in NIO and native transport 2014-02-27 13:56:15 +01:00
pom.xml Mark sun.nio.ch as optional 2014-04-23 10:37:39 +02:00
README.md Fix the 'branches to look' section 2014-01-16 14:37:54 +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.