hadoop-zookeeper-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From ph...@apache.org
Subject svn commit: r740141 - in /hadoop/zookeeper/trunk: CHANGES.txt docs/zookeeperProgrammers.html docs/zookeeperProgrammers.pdf src/docs/src/documentation/content/xdocs/zookeeperProgrammers.xml
Date Mon, 02 Feb 2009 23:00:04 GMT
Author: phunt
Date: Mon Feb  2 23:00:04 2009
New Revision: 740141

URL: http://svn.apache.org/viewvc?rev=740141&view=rev
Log:
programming guide watches section should clarify server/clientlib role in data/child watch
maint.

Modified:
    hadoop/zookeeper/trunk/CHANGES.txt
    hadoop/zookeeper/trunk/docs/zookeeperProgrammers.html
    hadoop/zookeeper/trunk/docs/zookeeperProgrammers.pdf
    hadoop/zookeeper/trunk/src/docs/src/documentation/content/xdocs/zookeeperProgrammers.xml

Modified: hadoop/zookeeper/trunk/CHANGES.txt
URL: http://svn.apache.org/viewvc/hadoop/zookeeper/trunk/CHANGES.txt?rev=740141&r1=740140&r2=740141&view=diff
==============================================================================
--- hadoop/zookeeper/trunk/CHANGES.txt (original)
+++ hadoop/zookeeper/trunk/CHANGES.txt Mon Feb  2 23:00:04 2009
@@ -148,6 +148,9 @@
    
    ZOOKEEPER-286. Make GenerateLoad use InstanceContainers. (breed via mahadev)
 
+   ZOOKEEPER-220. programming guide watches section should clarify
+   server/clientlib role in data/child watch maint. (breed via phunt)
+
 NEW FEATURES:
 
    ZOOKEEPER-276. Bookkeeper contribution (Flavio and Luca Telloli via mahadev)

Modified: hadoop/zookeeper/trunk/docs/zookeeperProgrammers.html
URL: http://svn.apache.org/viewvc/hadoop/zookeeper/trunk/docs/zookeeperProgrammers.html?rev=740141&r1=740140&r2=740141&view=diff
==============================================================================
--- hadoop/zookeeper/trunk/docs/zookeeperProgrammers.html (original)
+++ hadoop/zookeeper/trunk/docs/zookeeperProgrammers.html Mon Feb  2 23:00:04 2009
@@ -859,15 +859,21 @@
 </p>
 
         
-<p>This refers to the different ways a node can change. ZooKeeper
-        maintains two lists of watches: data watches and child watches.
-        getData() and exists() set data watches. getChildren() sets child
-        watches. Thus, setData() will trigger data watches for the znode being
-        set (assuming the set is successful). A successful create() will
-        trigger a data watch for the znode being created and a child watch for
-        the parent znode. A successful delete() will trigger both a data watch
-        and a child watch (since there can be no more children) for a znode
-        being deleted as well as a child watch for the parent znode.</p>
+<p>This refers to the different ways a node can change.  It
+        helps to think of ZooKeeper as maintaining two lists of
+        watches: data watches and child watches.  getData() and
+        exists() set data watches. getChildren() sets child
+        watches. Alternatively, it may help to think of watches being
+        set according to the kind of data returned. getData() and
+        exists() return information about the data of the node,
+        whereas getChildren() returns a list of children.  Thus,
+        setData() will trigger data watches for the znode being set
+        (assuming the set is successful). A successful create() will
+        trigger a data watch for the znode being created and a child
+        watch for the parent znode. A successful delete() will trigger
+        both a data watch and a child watch (since there can be no
+        more children) for a znode being deleted as well as a child
+        watch for the parent znode.</p>
       
 </li>
     

Modified: hadoop/zookeeper/trunk/docs/zookeeperProgrammers.pdf
URL: http://svn.apache.org/viewvc/hadoop/zookeeper/trunk/docs/zookeeperProgrammers.pdf?rev=740141&r1=740140&r2=740141&view=diff
==============================================================================
Binary files - no diff available.

Modified: hadoop/zookeeper/trunk/src/docs/src/documentation/content/xdocs/zookeeperProgrammers.xml
URL: http://svn.apache.org/viewvc/hadoop/zookeeper/trunk/src/docs/src/documentation/content/xdocs/zookeeperProgrammers.xml?rev=740141&r1=740140&r2=740141&view=diff
==============================================================================
--- hadoop/zookeeper/trunk/src/docs/src/documentation/content/xdocs/zookeeperProgrammers.xml
(original)
+++ hadoop/zookeeper/trunk/src/docs/src/documentation/content/xdocs/zookeeperProgrammers.xml
Mon Feb  2 23:00:04 2009
@@ -467,15 +467,21 @@
         <para><emphasis role="bold">The data for which the watch was
         set</emphasis></para>
 
-        <para>This refers to the different ways a node can change. ZooKeeper
-        maintains two lists of watches: data watches and child watches.
-        getData() and exists() set data watches. getChildren() sets child
-        watches. Thus, setData() will trigger data watches for the znode being
-        set (assuming the set is successful). A successful create() will
-        trigger a data watch for the znode being created and a child watch for
-        the parent znode. A successful delete() will trigger both a data watch
-        and a child watch (since there can be no more children) for a znode
-        being deleted as well as a child watch for the parent znode.</para>
+        <para>This refers to the different ways a node can change.  It
+        helps to think of ZooKeeper as maintaining two lists of
+        watches: data watches and child watches.  getData() and
+        exists() set data watches. getChildren() sets child
+        watches. Alternatively, it may help to think of watches being
+        set according to the kind of data returned. getData() and
+        exists() return information about the data of the node,
+        whereas getChildren() returns a list of children.  Thus,
+        setData() will trigger data watches for the znode being set
+        (assuming the set is successful). A successful create() will
+        trigger a data watch for the znode being created and a child
+        watch for the parent znode. A successful delete() will trigger
+        both a data watch and a child watch (since there can be no
+        more children) for a znode being deleted as well as a child
+        watch for the parent znode.</para>
       </listitem>
     </itemizedlist>
 



Mime
View raw message