Go to file
Ruwei 6cd9617311 add AUTH & EMPTY to SmtpCommand (#9999)
Motivation:
AUTH command is used to login to a SMTP server.
EMPTY command is for request with only parameter.

Modifications:
Add AUTH & EMPTY to SmtpCommand & SmtpRequests
Update SmtpRequestEncoder#writeParameters, handle SP according to
command
Add unit test

Result:
fix #9995
2020-02-07 14:30:16 +01:00
.github
.mvn
all Use latest checkstyle version for all artifact as well. 2020-02-05 10:10:23 +01:00
bom
buffer Fix incorrect property name in PooledByteBufAllocator 2020-02-05 14:40:08 +01:00
codec
codec-dns
codec-haproxy
codec-http Added tests for Transfer-Encoding header with whitespace (#9997) 2020-02-05 14:34:14 +01:00
codec-http2 Ensure ChannelOptions are applied in the same order as configured in Http2StreamChannelBootstrap (#9998) (#10001) 2020-02-07 09:19:10 +01:00
codec-memcache
codec-mqtt
codec-redis
codec-smtp add AUTH & EMPTY to SmtpCommand (#9999) 2020-02-07 14:30:16 +01:00
codec-socks
codec-stomp
codec-xml
common
dev-tools
docker
example
handler Add SslClientHelloHandler which allows to do something based on the S… (#9827) 2020-02-05 14:57:05 +01:00
handler-proxy
license
microbench
resolver
resolver-dns
resolver-dns-native-macos
tarball
testsuite
testsuite-autobahn
testsuite-http2
testsuite-native-image
testsuite-osgi
testsuite-shading
transport Ensure ChannelOptions are applied in the same order as configured in *Bootstrap (#9998) 2020-02-06 09:18:52 +01:00
transport-blockhound-tests
transport-native-epoll Copy IPV6-mapped-IPV4 addresses correctly in native code (#9996) 2020-02-05 15:41:16 +01:00
transport-native-kqueue
transport-native-unix-common
transport-native-unix-common-tests
transport-sctp
.fbprefs
.gitattributes
.gitignore
.lgtm.yml
CONTRIBUTING.md
LICENSE.txt
NOTICE.txt
README.md
mvnw
mvnw.cmd
pom.xml Add SslClientHelloHandler which allows to do something based on the S… (#9827) 2020-02-05 14:57:05 +01:00
run-example.sh

README.md

Netty Project

Netty is an asynchronous event-driven network application framework for rapid development of maintainable high performance protocol servers & clients.

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

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.0 resides in the branch '3.9' and the branch '4.0' 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.