You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@zookeeper.apache.org by "Benjamin Reed (JIRA)" <ji...@apache.org> on 2010/04/05 16:51:27 UTC

[jira] Updated: (ZOOKEEPER-733) use netty to handle client connections

     [ https://issues.apache.org/jira/browse/ZOOKEEPER-733?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Benjamin Reed updated ZOOKEEPER-733:
------------------------------------

    Attachment: ZOOKEEPER-733.patch

this is an initial cut at integrating netty. it is stale and still fails two tests, but i don't want to lose track of it.

svn info gives the following:

URL: https://svn.apache.org/repos/asf/hadoop/zookeeper/trunk/src/java
Repository Root: https://svn.apache.org/repos/asf
Repository UUID: 13f79535-47bb-0310-9956-ffa450edef68
Revision: 823252
Node Kind: directory
Schedule: normal
Last Changed Author: mahadev
Last Changed Rev: 817885
Last Changed Date: 2009-09-22 15:59:34 -0700 (Tue, 22 Sep 2009)

> use netty to handle client connections
> --------------------------------------
>
>                 Key: ZOOKEEPER-733
>                 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-733
>             Project: Zookeeper
>          Issue Type: Improvement
>            Reporter: Benjamin Reed
>         Attachments: ZOOKEEPER-733.patch
>
>
> 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.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.