This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.

Bug 9095 - WS-Enumeration - Calling Pull or Release operations after EndOfSequence has been issued
Summary: WS-Enumeration - Calling Pull or Release operations after EndOfSequence has b...
Alias: None
Product: WS-Resource Access
Classification: Unclassified
Component: Enumeration (show other bugs)
Version: LC
Hardware: PC Windows NT
: P2 normal
Target Milestone: ---
Assignee: Ram Jeyaraman
QA Contact: notifications mailing list for WS Resource Access
Depends on:
Reported: 2010-02-20 00:09 UTC by Ram Jeyaraman
Modified: 2010-07-27 20:28 UTC (History)
1 user (show)

See Also:


Description Ram Jeyaraman 2010-02-20 00:09:37 UTC
WS-Enumeration already states [1] in section 3. The enumeration context will become invalid once EndOfSequence is issued. Given that, I suggest removing [2].
An enumeration context can become invalid for any reason including: 
Enumeration completed (i.e. an EndOfSequence has been returned in a Pull response) 
Enumeration released 
Enumeration expired 
Enumeration ended (i.e. ended via an EnumerationEnd message from data source 
Enumeration context replaced in the response to another Pull request 
In addition, the data source MAY invalidate an enumeration context at any time, as necessary. 
When processing a Pull, Renew, GetStatus or Release operation, a data source MUST generate an wsen:InvalidEnumerationContext fault if it determines that the enumeration context supplied by the consumer in the request is invalid.
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.
Comment 1 Doug Davis 2010-03-02 02:48:42 UTC
There really are two different concepts being discussed in the quoted
text.  In [1] it says what a Data Source MUST do in the case of receiving
a msg with an invalid context.  The text in [2] is different, its talking
about what the Consumer MUST (or MUST NOT) do once it knows the enumeration
is invalid. These are two very different thing.  

I'm ok with remove the text in [2], but only if we add something to the
generic section (like after the text in [1]) that says something like:
Once a Consumer determines that an enumeration context is invalid, it
MUST NOT issue any more WS-Enumeration request messages referencing
that enumeration context.

This will prevent any confusion as to what the expectations are for the
Consumer.  For example, does it need to perform any clean up by sending
a Release to the Data Source?
Comment 2 Robert Freund 2010-03-30 19:52:44 UTC
Resolved with comment #1