Mailing-List: contact dev-help@zookeeper.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@zookeeper.apache.org
Date: Thu, 7 Jul 2011 06:41:21 +0000 (UTC)
From: "Mahadev konar (JIRA)" <jira@apache.org>
To: dev@zookeeper.apache.org
Message-ID: 
 <556326729.6327.1310020881250.JavaMail.tomcat@hel.zones.apache.org>
Subject: [jira] [Commented] (ZOOKEEPER-781) provide a generalized
 "connection strategy" for ZooKeeper clients
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


    [ https://issues.apache.org/jira/browse/ZOOKEEPER-781?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13061069#comment-13061069 ] 

Mahadev konar commented on ZOOKEEPER-781:
-----------------------------------------

Qian,
 Any update on this?

> provide a generalized "connection strategy" for ZooKeeper clients
> -----------------------------------------------------------------
>
>                 Key: ZOOKEEPER-781
>                 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-781
>             Project: ZooKeeper
>          Issue Type: New Feature
>          Components: c client, java client
>            Reporter: Patrick Hunt
>            Assignee: Qian Ye
>             Fix For: 3.4.0
>
>         Attachments: ZOOKEEPER-781.patch, ZOOKEEPER-781.patch, ZOOKEEPER-781.patch, ZOOKEEPER-781.patch, ZOOKEEPER-781.patch, ZOOKEEPER-781.patch
>
>
> A connection strategy allows control over the way that ZooKeeper clients (we would implement this for both c and java apis) connect to a serving ensemble. Today we have two strategies, randomized round robin (default) and ordered round robin, both of which are hard coded into the client implementation. We would generalize this interface and allow users to create their own.
> See this page for more detail: http://wiki.apache.org/hadoop/ZooKeeper/ConnectionStrategy

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira