[
https://issues.apache.org/jira/browse/ZOOKEEPER-823?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12920737#action_12920737
]
Patrick Hunt commented on ZOOKEEPER-823:
----------------------------------------
Thomas (also Mahadev and other committers)
Here's an idea. What if we setup a branch in SVN with these changes (netty). It
would be a short lived branch. Then we can setup a new job on apache hudson,
and just keep hammering on that thing until we get all the issues (intermittent
bugs) resolved.
How's that sound?
An alternative would be to use Git but apache hudson doesn't allow that. I'd
create/maintain the svn branch (you need to be a committer).
> update ZooKeeper java client to optionally use Netty for connections
> --------------------------------------------------------------------
>
> Key: ZOOKEEPER-823
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-823
> Project: Zookeeper
> Issue Type: New Feature
> Components: java client
> Reporter: Patrick Hunt
> Assignee: Patrick Hunt
> Fix For: 3.4.0
>
> Attachments: NettyNettySuiteTest.rtf,
> TEST-org.apache.zookeeper.test.NettyNettySuiteTest.txt.gz,
> testDisconnectedAddAuth_FAILURE, testWatchAutoResetWithPending_FAILURE,
> ZOOKEEPER-823.patch, ZOOKEEPER-823.patch, ZOOKEEPER-823.patch,
> ZOOKEEPER-823.patch, ZOOKEEPER-823.patch, ZOOKEEPER-823.patch,
> ZOOKEEPER-823.patch, ZOOKEEPER-823.patch, ZOOKEEPER-823.patch,
> ZOOKEEPER-823.patch
>
>
> This jira will port the client side connection code to use netty rather than
> direct nio.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
