You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@zookeeper.apache.org by "Patrick Datko (JIRA)" <ji...@apache.org> on 2010/08/11 16:52:17 UTC
[jira] Created: (ZOOKEEPER-838) Chroot is an attribute of
ClientCnxn
Chroot is an attribute of ClientCnxn
------------------------------------
Key: ZOOKEEPER-838
URL: https://issues.apache.org/jira/browse/ZOOKEEPER-838
Project: Zookeeper
Issue Type: Sub-task
Reporter: Patrick Datko
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (ZOOKEEPER-838) Chroot is an attribute of
ClientCnxn
Posted by "Thomas Koch (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/ZOOKEEPER-838?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12897725#action_12897725 ]
Thomas Koch commented on ZOOKEEPER-838:
---------------------------------------
I need to change the internal logic of watch registration: The watches will now be registered under the full serverPath, since we want to have multiple ChangeRoots in the client. For each watcher I'll additionally save its ChRoot in the watchManager.
> Chroot is an attribute of ClientCnxn
> ------------------------------------
>
> Key: ZOOKEEPER-838
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-838
> Project: Zookeeper
> Issue Type: Sub-task
> Reporter: Patrick Datko
>
> It would be better to have one process that uses ZooKeeper for different things
> (managing a list of work, locking some unrelated locks elsewhere). So there are
> components that do this work inside the same process. These components should
> get the same zookeeper-client reference chroot'ed for their needs.
> So it'd be much better, if the ClientCnxn would not care about the chroot.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (ZOOKEEPER-838) Chroot is an attribute of
ClientCnxn
Posted by "Patrick Datko (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/ZOOKEEPER-838?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Patrick Datko updated ZOOKEEPER-838:
------------------------------------
Tags: chroot
Description:
It would be better to have one process that uses ZooKeeper for different things
(managing a list of work, locking some unrelated locks elsewhere). So there are
components that do this work inside the same process. These components should
get the same zookeeper-client reference chroot'ed for their needs.
So it'd be much better, if the ClientCnxn would not care about the chroot.
> Chroot is an attribute of ClientCnxn
> ------------------------------------
>
> Key: ZOOKEEPER-838
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-838
> Project: Zookeeper
> Issue Type: Sub-task
> Reporter: Patrick Datko
>
> It would be better to have one process that uses ZooKeeper for different things
> (managing a list of work, locking some unrelated locks elsewhere). So there are
> components that do this work inside the same process. These components should
> get the same zookeeper-client reference chroot'ed for their needs.
> So it'd be much better, if the ClientCnxn would not care about the chroot.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.