andreacavalli/netty5
1
0
Fork 0
Code Issues Pull Requests Projects Releases Wiki Activity
3,283 Commits 27 Branches 234 Tags 84 MiB
Java 99.8%
Shell 0.1%
6398964b89
Go to file
Trustin Lee 6398964b89 Fix incorrect port range check 
Motivation:

In the Internet Protocol, the valid port number range is from 1 to 65535
(inclusive on the both side.)  However, SocksCmdRequest refuses to
construct itself when the port number 65535 is specified.

Modification:

Do not raise an exception when the specified port number is 65535.

Result:

Fixes #2428
2014-04-29 18:00:40 +09:00
license Update notices for WebSocket support. 2011-12-09 16:15:41 +11:00
src Fix incorrect port range check 2014-04-29 18:00:40 +09:00
.fbfilter.xml Update license headers 2012-06-04 13:35:22 -07:00
.fbprefs Updated Find Bugs configuration 2009-03-04 10:33:09 +00:00
.gitignore Adds the IntelliJ project directory to .gitignore. 2012-08-09 08:11:17 +10:00
.travis.yml Travis CI branch whitelisting 2013-03-11 09:54:35 +09:00
CONTRIBUTING.md Move the pull request guide to the developer guide 2014-03-12 13:18:38 +09:00
LICENSE.txt Relicensed to Apache License v2 2009-08-28 07:15:49 +00:00
NOTICE.txt More license updates 2011-12-09 14:31:04 +09:00
pom.xml [maven-release-plugin] prepare for next development iteration 2013-12-22 19:45:29 +09:00
README.md Add README.md 2014-01-16 14:40:07 +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.