[JAVA-3037] Move Netty stream support to a separate module Created: 08/Oct/18 Updated: 01/Apr/19 Resolved: 01/Apr/19 |
|
| Status: | Closed |
| Project: | Java Driver |
| Component/s: | Async |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Jeffrey Yemin | Assignee: | Unassigned |
| Resolution: | Won't Fix | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||
| Description |
|
Currently both driver-core and driver-async take a direct dependency on Netty. Consider moving that dependency to a separate mongodb-driver-netty module, and requiring explicit programmatic enablement of Netty via NettyStreamFactoryFactory. This should only be done along with the addition of built-in async support for TLS so that Netty is no longer required to connect to TLS deployments via the async drivers. |