[
https://issues.apache.org/jira/browse/ZOOKEEPER-1290?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13144583#comment-13144583
]
Patrick Hunt commented on ZOOKEEPER-1290:
-----------------------------------------
You'll be bounded by the session timeout. That's acceptable?
Also it would be good if you add to both c and java given we want to maintain
feature parity btw the clients.
> 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