andreacavalli/netty5
1
0
Fork 0
Code Issues Pull Requests Projects Releases Wiki Activity
6,296 Commits 27 Branches 234 Tags 84 MiB
Java 99.8%
Shell 0.1%
afe4833e4e
Go to file
Trustin Lee afe4833e4e Add ApplicationProtocolConfig.DISABLED 
Motivation:

When ALPN/NPN is disabled, a user has to instantiate a new
ApplicationProtocolConfig with meaningless parameters.

Modifications:

- Add ApplicationProtocolConfig.DISABLED, the singleton instance
- Reject the constructor calls with Protocol.NONE, which doesn't make
  much sense because a user should use DISABLED instead.

Result:

More user-friendly API when ALPN/NPN is not needed by a user.
2014-10-31 14:14:10 +09:00
all Fix missing version properties of transport-epoll in all-in-one JAR 2014-10-21 22:36:19 +09:00
buffer Disable caching of PooledByteBuf for different threads. 2014-09-22 13:39:42 +02:00
codec Headers Cleanup 2014-10-22 09:26:31 -04:00
codec-dns Add EDNS support to DnsQueryEncoder 2014-10-16 17:06:20 +09:00
codec-haproxy Fix NPE problems 2014-07-20 12:55:08 +02:00
codec-http Added an option to use websockets without masking 2014-10-25 22:17:41 +09:00
codec-http2 HTTP/2 Send GOAWAY if no more stream ids 2014-10-26 08:48:23 -04:00
codec-memcache Add proxy support for client socket connections 2014-10-14 12:40:33 +09:00
codec-mqtt Add proxy support for client socket connections 2014-10-14 12:40:33 +09:00
codec-socks Add proxy support for client socket connections 2014-10-14 12:40:33 +09:00
codec-stomp Netty Headers Class Restructure and Algorithm Updates 2014-10-21 13:04:08 -04:00
common Netty Headers Class Restructure and Algorithm Updates 2014-10-21 13:04:08 -04:00
example ALPN should allow handshake failure if no compatible protocols found 2014-10-30 19:39:31 -04:00
handler Add ApplicationProtocolConfig.DISABLED 2014-10-31 14:14:10 +09:00
handler-proxy Netty Headers Class Restructure and Algorithm Updates 2014-10-21 13:04:08 -04:00
license Implemented LZMA frame encoder 2014-09-15 15:14:15 +02:00
microbench IPv6 address to string rfc5952 2014-09-22 20:30:14 -04:00
resolver Name resolver API and DNS-based name resolver 2014-10-16 17:10:36 +09:00
resolver-dns Improve DnsNameResolverTest.testResolveA() 2014-10-25 17:29:59 +09:00
tarball [maven-release-plugin] prepare for next development iteration 2013-12-22 22:06:15 +09:00
testsuite Fix an infinite loop when writing a zero-length FileRegion 2014-10-17 16:04:37 +09:00
transport Implement user-defined writability flags 2014-10-25 15:58:52 +09:00
transport-native-epoll Name resolver API and DNS-based name resolver 2014-10-16 17:10:36 +09:00
transport-rxtx Fix most inspector warnings 2014-07-02 19:04:11 +09:00
transport-sctp Allow to obtain RecvByteBufAllocator.Handle to allow more flexible implementations 2014-08-12 06:54:29 +02:00
transport-udt Name resolver API and DNS-based name resolver 2014-10-16 17:10:36 +09:00
.fbprefs Updated Find Bugs configuration 2009-03-04 10:33:09 +00:00
.gitignore Exclude bin directory from git Motivation: 2014-08-27 06:33:22 +02: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 Implemented LZMA frame encoder 2014-09-15 15:14:15 +02:00
pom.xml ALPN should allow handshake failure if no compatible protocols found 2014-10-30 19:39:31 -04:00
README.md Add a link to the 'native transports' page 2014-07-21 12:10:16 -07:00
run-example.sh ALPN java implementation 2014-08-30 13:41:07 -04: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.