[
https://issues.apache.org/jira/browse/ZOOKEEPER-1290?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13144591#comment-13144591
]
Marc Celani commented on ZOOKEEPER-1290:
----------------------------------------
Patrick,
I'm not sure I'm understanding your comment about being bounded to the session
timeout. My implementation of init_with_watches is exactly the same as
zookeeper_init except that it will initialize the watch hash tables with values
and the last_zxid with a given value. On connect, the current c implementation
will send the set watches for me (even though it is not a reconnect). It will
still require a session timeout be given and will respect it. It's not clear to
me what my change has to do with session timeouts.
Adding to java sounds reasonable.
Marc
> zookeeper_init_with_watches
> ---------------------------
>
> Key: ZOOKEEPER-1290
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-1290
> Project: ZooKeeper
> Issue Type: New Feature
> Components: c client
> Reporter: Marc Celani
>
> Our use of zookeeper requires high scalability, and the underlying data set
> is small and changes infrequently. A persisted cache is ideal for solving
> scalability. We want to treat a restart as if it were a prolonged reconnect -
> that is, maintain the last known zxid and watch list. We would like to expose
> a new zookeeper_init_with_watches api that allows the zhandle to be
> initialized with the watch list and last known zxid. The change would reuse
> the current reconnect logic.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
