zookeeper-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From br...@apache.org
Subject svn commit: r1146820 - in /zookeeper/trunk: CHANGES.txt src/c/include/zookeeper.h
Date Thu, 14 Jul 2011 17:53:52 GMT
Author: breed
Date: Thu Jul 14 17:53:51 2011
New Revision: 1146820

URL: http://svn.apache.org/viewvc?rev=1146820&view=rev
Log:
ZOOKEEPER-782. Incorrect C API documentation for Watches

Modified:
    zookeeper/trunk/CHANGES.txt
    zookeeper/trunk/src/c/include/zookeeper.h

Modified: zookeeper/trunk/CHANGES.txt
URL: http://svn.apache.org/viewvc/zookeeper/trunk/CHANGES.txt?rev=1146820&r1=1146819&r2=1146820&view=diff
==============================================================================
--- zookeeper/trunk/CHANGES.txt (original)
+++ zookeeper/trunk/CHANGES.txt Thu Jul 14 17:53:51 2011
@@ -245,6 +245,8 @@ BUGFIXES: 
   
   ZOOKEEPER-1046. Small fix: Creating a new sequential node results in a ZNODEEXISTS error.
(Vishal K via camille)
 
+  ZOOKEEPER-782. Incorrect C API documentation for Watches. (mahadev via breed)
+
 IMPROVEMENTS:
   ZOOKEEPER-724. Improve junit test integration - log harness information 
   (phunt via mahadev)

Modified: zookeeper/trunk/src/c/include/zookeeper.h
URL: http://svn.apache.org/viewvc/zookeeper/trunk/src/c/include/zookeeper.h?rev=1146820&r1=1146819&r2=1146820&view=diff
==============================================================================
--- zookeeper/trunk/src/c/include/zookeeper.h (original)
+++ zookeeper/trunk/src/c/include/zookeeper.h Thu Jul 14 17:53:51 2011
@@ -42,11 +42,9 @@
  * ZooKeeper clients can leave watches when they queries the data or children
  * of a node. If a watch is left, that client will be notified of the change.
  * The notification is a one time trigger. Subsequent chances to the node will
- * not trigger a notification unless the client issues a querity with the watch
- * flag set. 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.
+ * not trigger a notification unless the client issues a query with the watch
+ * flag set. If the client is ever disconnected from the service, the watches do 
+ * not need to be reset. The client automatically resets the watches.
  * 
  * When a node is created, it may be flagged as an ephemeral node. Ephemeral
  * nodes are automatically removed when a client session is closed or when



Mime
View raw message