E M P E R O R

Networks • Arch • Exec

Native Fork for Netty

See our wiki page.

Usage

Emperor 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.