[
https://issues.apache.org/jira/browse/ZOOKEEPER-2072?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14192862#comment-14192862
]
Hongchao Deng commented on ZOOKEEPER-2072:
------------------------------------------
[~iandi]
As I mentioned, I uploaded my previous work to coordinate..
I would like to separate the work into:
1. ZOOKEEPER-2069: Netty Client
2. ZOOKEEPER-2072: set channelpipeline factory
3. ZOOKEEPER-2068: test failure for netty server
4. more problems.
Once we are confident that Netty connection is working great, we will get
pluggable SSL.
How does my plan sound? Let me know your thoughts.
> Netty Server Should Configure Child Channel Pipeline By Specifying
> ChannelPipelineFactory
> -----------------------------------------------------------------------------------------
>
> Key: ZOOKEEPER-2072
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2072
> Project: ZooKeeper
> Issue Type: Bug
> Components: server
> Reporter: Hongchao Deng
> Assignee: Hongchao Deng
> Attachments: ZOOKEEPER-2072.patch, test-jenkins.patch
>
>
> Currently, netty server is setting up child channel in this way:
> {code}
> bootstrap.getPipeline().addLast("servercnxnfactory", channelHandler);
> {code}
> According to the [netty
> doc|http://netty.io/3.9/api/org/jboss/netty/bootstrap/ServerBootstrap.html],
> bq. you cannot use this approach if you are going to open more than one
> Channels or run a server that accepts incoming connections to create its
> child channels.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
