Description
we currently have our own asynchronous NIO socket engine to be able to handle lots of clients with a single thread. over time the engine has become more complicated. we would also like the engine to use multiple threads on machines with lots of cores. plus, we would like to be able to support things like SSL. if we switch to netty, we can simplify our code and get the previously mentioned benefits.
Attachments
Attachments
Issue Links
- is related to
-
AVRO-405 Netty-based Java RPC server
- Closed
- relates to
-
ZOOKEEPER-2737 NettyServerCnxFactory leaks connection if exception happens while writing to a channel.
- Closed
-
ZOOKEEPER-823 update ZooKeeper java client to optionally use Netty for connections
- Closed
-
ZOOKEEPER-845 remove duplicate code from netty and nio ServerCnxn classes
- Resolved