2c3d263e23
Motivation: This is a PR to solve the problem described here: https://github.com/netty/netty/issues/9767 Basically this PR is to add two more APIs in SslContextBuilder, for users to directly specify the KeyManager or TrustManager they want to use when building SslContext. This is very helpful when users want to pass in some customized implementation of KeyManager or TrustManager. Modification: This PR takes the first approach in here: https://github.com/netty/netty/issues/9767#issuecomment-551927994 (comment) which is to immediately convert the managers into factories and let factories continue to pass through Netty. 1. Add in SslContextBuilder the two APIs mentioned above 2. Create a KeyManagerFactoryWrapper and a TrustManagerFactoryWrapper, which take a KeyManager and a TrustManager respectively. These are two simple wrappers that do the conversion from XXXManager class to XXXManagerFactory class 3.Create a SimpleKeyManagerFactory class(and internally X509KeyManagerWrapper for compatibility), which hides the unnecessary details such as KeyManagerFactorySpi. This serves the similar functionalities with SimpleTrustManagerFactory, which was already inside Netty. Result: Easier usage.
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:
- Latest stable Oracle JDK 7
- Latest stable Apache Maven
- If you are on Linux, you need additional development packages installed on your system, because you'll build the native transport.
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.allio.netty.bufferio.netty.codecio.netty.codec.dnsio.netty.codec.haproxyio.netty.codec.httpio.netty.codec.http2io.netty.codec.memcacheio.netty.codec.mqttio.netty.codec.redisio.netty.codec.smtpio.netty.codec.socksio.netty.codec.stompio.netty.codec.xmlio.netty.commonio.netty.handlerio.netty.handler.proxyio.netty.resolverio.netty.resolver.dnsio.netty.transportio.netty.transport.epoll(nativeomitted - reserved keyword in Java)io.netty.transport.kqueue(nativeomitted - reserved keyword in Java)io.netty.transport.unix.common(nativeomitted - reserved keyword in Java)io.netty.transport.rxtxio.netty.transport.sctpio.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.