[
https://issues.apache.org/jira/browse/ZOOKEEPER-4835?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17850052#comment-17850052
]
David Smiley commented on ZOOKEEPER-4835:
-----------------------------------------
Note that TLS can be achieved completely independently via Mesh/Istio.
{quote} that the zookeeper client really works without any Netty
{quote}
It's not clear how to make a "client" vs "server" distinction within the
codebase to enforce that it's okay for the "server" to talk to Netty but not
the "client". Plenty of packages are in common (utils). Anyway, as the
ArchUnit test shows, it's really pretty close to making a class name based
distinction of which classes can talk to Netty.
> Netty should be an optional dependency
> --------------------------------------
>
> Key: ZOOKEEPER-4835
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-4835
> Project: ZooKeeper
> Issue Type: Improvement
> Reporter: David Smiley
> Priority: Major
> Attachments: zk-netty-violations.txt
>
>
> ZK should not mandate the inclusion of Netty if Netty features aren't being
> used. There are very few usages of Netty from ZK files that are not named
> Netty, so this looks pretty easy.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
