Skip to content
/ netty Public
forked from netty/netty

Netty project - an event-driven asynchronous network application framework

License

Notifications You must be signed in to change notification settings

Kvicii/netty

This branch is 894 commits behind netty/netty:4.1.

Folders and files

NameName
Last commit message
Last commit date
Jul 4, 2022
Apr 21, 2022
Jul 11, 2022
Jul 11, 2022
Jul 19, 2022
Jul 11, 2022
Jul 11, 2022
Jul 14, 2022
Jul 11, 2022
Jul 11, 2022
Jul 11, 2022
Jul 11, 2022
Jul 11, 2022
Jul 11, 2022
Jul 11, 2022
Jul 11, 2022
Jul 11, 2022
Jul 11, 2022
Jul 11, 2022
May 16, 2022
Jul 11, 2022
Jul 11, 2022
Jul 11, 2022
Jul 8, 2021
Jul 11, 2022
Jul 11, 2022
Jul 20, 2022
Jul 11, 2022
Jul 11, 2022
Jul 20, 2022
Jul 11, 2022
Jul 11, 2022
Jul 11, 2022
Jul 11, 2022
Jul 11, 2022
Jul 11, 2022
Jul 11, 2022
Jul 11, 2022
Jul 17, 2022
Jul 11, 2022
Jul 17, 2022
Jul 17, 2022
Jul 17, 2022
Jul 20, 2022
Jul 11, 2022
Jul 20, 2022
Jul 11, 2022
Jul 11, 2022
Jul 11, 2022
Jul 17, 2022
Mar 4, 2009
Jan 26, 2018
Oct 7, 2021
Jan 17, 2020
Jul 9, 2019
Oct 23, 2020
Jul 8, 2021
Mar 8, 2022
Nov 16, 2021
Oct 23, 2020
Oct 23, 2020
Jan 1, 2021
Oct 23, 2020
Jul 20, 2022
May 19, 2021

Repository files navigation

Build project

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+ / 4.1+) is enough to run your Netty-based application.

Branches to look

Development of all versions takes place in each branch whose name is identical to <majorVersion>.<minorVersion>. For example, the development of 3.9 and 4.1 resides in the branch '3.9' and the branch '4.1' respectively.

Usage with JDK 9+

Netty can be used in modular JDK9+ applications as a collection of automatic modules. The module names follow the reverse-DNS style, and are derived from subproject names rather than root packages due to historical reasons. They are listed below:

  • io.netty.all
  • io.netty.buffer
  • io.netty.codec
  • io.netty.codec.dns
  • io.netty.codec.haproxy
  • io.netty.codec.http
  • io.netty.codec.http2
  • io.netty.codec.memcache
  • io.netty.codec.mqtt
  • io.netty.codec.redis
  • io.netty.codec.smtp
  • io.netty.codec.socks
  • io.netty.codec.stomp
  • io.netty.codec.xml
  • io.netty.common
  • io.netty.handler
  • io.netty.handler.proxy
  • io.netty.resolver
  • io.netty.resolver.dns
  • io.netty.transport
  • io.netty.transport.epoll (native omitted - reserved keyword in Java)
  • io.netty.transport.kqueue (native omitted - reserved keyword in Java)
  • io.netty.transport.unix.common (native omitted - reserved keyword in Java)
  • io.netty.transport.rxtx
  • io.netty.transport.sctp
  • io.netty.transport.udt

Automatic modules do not provide any means to declare dependencies, so you need to list each used module separately in your module-info file.

About

Netty project - an event-driven asynchronous network application framework

Resources

License

Security policy

Stars

Watchers

Forks

Packages

No packages published

Languages

  • Java 98.6%
  • C 1.1%
  • HTML 0.1%
  • Shell 0.1%
  • JavaScript 0.1%
  • Makefile 0.0%