- From: Doug Davis via cvs-syncmail <cvsmail@w3.org>
- Date: Tue, 30 Mar 2010 20:49:33 +0000
- To: public-ws-resource-access-notifications@w3.org
Update of /w3ccvs/WWW/2002/ws/ra/edcopies
In directory hutz:/tmp/cvs-serv25055
Modified Files:
wsenum.html wsenum.xml
Log Message:
9095
Index: wsenum.html
===================================================================
RCS file: /w3ccvs/WWW/2002/ws/ra/edcopies/wsenum.html,v
retrieving revision 1.123
retrieving revision 1.124
diff -u -d -r1.123 -r1.124
--- wsenum.html 17 Mar 2010 03:22:16 -0000 1.123
+++ wsenum.html 30 Mar 2010 20:49:31 -0000 1.124
@@ -367,6 +367,10 @@
enumeration context is invalid, especially if all of the state
associated with the enumeration is kept in the enumeration context
and refreshed on every PullResponse or RenewResponse.
+ </p><p>
+ Once a consumer determines that an enumeration context is invalid, it
+ MUST NOT issue any more WS-Enumeration request messages referencing
+ that enumeration context.
</p><div class="div2">
<h3><a name="Enumerate" id="Enumerate"/>3.1 Enumerate</h3><p>
This specification defines the Enumerate operation to start an enumeration.
@@ -842,13 +846,6 @@
returned by this Pull request. The presence of a wsen:EndOfSequence
element (line (24)) indicates that no more elements are available
and that the enumeration context is now invalid.
- </p><p>
- The consumer MUST NOT issue additional Pull
- request messages after a Pull response containing a
- wsen:EndOfSequence element has been received. Similarly, upon
- receipt of a Pull response containing a wsen:EndOfSequence element,
- the consumer MUST NOT issue a Release operation to signal that
- the enumeration context is no longer needed.
</p></div><div class="div2">
<h3><a name="Renew" id="Renew"/>3.3 Renew</h3><p>
To update, or renew, the expiration for an enumeration, a Renew
@@ -2130,4 +2127,5 @@
<a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=6463">6463</a>,
<a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=8031">8031</a>,
<a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=8198">8198</a></td></tr><tr><td> 2010/03/16 </td><td> DD </td><td> Added resolution of issue
- <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=8886">8886</a></td></tr></tbody></table></div></div></body></html>
\ No newline at end of file
+ <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=8886">8886</a></td></tr><tr><td> 2010/03/30 </td><td> DD </td><td> Added resolution of issue
+ <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=9095">9095</a></td></tr></tbody></table></div></div></body></html>
\ No newline at end of file
Index: wsenum.xml
===================================================================
RCS file: /w3ccvs/WWW/2002/ws/ra/edcopies/wsenum.xml,v
retrieving revision 1.114
retrieving revision 1.115
diff -u -d -r1.114 -r1.115
--- wsenum.xml 17 Mar 2010 03:22:16 -0000 1.114
+++ wsenum.xml 30 Mar 2010 20:49:31 -0000 1.115
@@ -635,6 +635,12 @@
and refreshed on every PullResponse or RenewResponse.
</p>
+ <p>
+ Once a consumer determines that an enumeration context is invalid, it
+ MUST NOT issue any more WS-Enumeration request messages referencing
+ that enumeration context.
+ </p>
+
<div2 id="Enumerate">
<head>Enumerate</head>
@@ -1383,14 +1389,6 @@
and that the enumeration context is now invalid.
</p>
- <p>
- The consumer MUST NOT issue additional Pull
- request messages after a Pull response containing a
- wsen:EndOfSequence element has been received. Similarly, upon
- receipt of a Pull response containing a wsen:EndOfSequence element,
- the consumer MUST NOT issue a Release operation to signal that
- the enumeration context is no longer needed.
- </p>
</div2>
<div2 id="Renew">
@@ -4012,6 +4010,13 @@
<loc href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=8886">8886</loc>
</td>
</tr>
+ <tr>
+ <td> 2010/03/30 </td>
+ <td> DD </td>
+ <td> Added resolution of issue
+ <loc href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=9095">9095</loc>
+ </td>
+ </tr>
</tbody>
</table>
</div1>
Received on Tuesday, 30 March 2010 20:49:35 UTC