You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@zookeeper.apache.org by "Mahadev konar (JIRA)" <ji...@apache.org> on 2011/07/13 23:47:00 UTC

[jira] [Updated] (ZOOKEEPER-782) Incorrect C API documentation for Watches

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

Mahadev konar updated ZOOKEEPER-782:
------------------------------------

    Attachment: ZOOKEEPER-782.patch

Documentation change. 

> Incorrect C API documentation for Watches
> -----------------------------------------
>
>                 Key: ZOOKEEPER-782
>                 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-782
>             Project: ZooKeeper
>          Issue Type: Bug
>          Components: c client, documentation
>    Affects Versions: 3.3.1
>            Reporter: Dave Wright
>            Priority: Trivial
>             Fix For: 3.4.0
>
>         Attachments: ZOOKEEPER-782.patch
>
>
>  The C API Doxygen documentation states:
> " .... If the client is ever disconnected from the service, even if the
>   disconnection is temporary, the watches of the client will be removed from
>   the service, so a client must treat a disconnect notification as an implicit
>   trigger of all outstanding watches."
> This is incorrect as of v.3. Watches are only lost and need to be re-registered when a session times out. When a normal disconnection occurs watches are reset automatically on reconnection.
> The documentation in zookeeper.h needs to be updated to correct this explanation.

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