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 6956 - Enum: server behavior after end of enumeration context reached
Summary: Enum: server behavior after end of enumeration context reached
Status: CLOSED REMIND
Alias: None
Product: WS-Resource Access
Classification: Unclassified
Component: Enumeration (show other bugs)
Version: FPWD
Hardware: PC Windows NT
: P2 normal
Target Milestone: ---
Assignee: Geoff Bullen
QA Contact: notifications mailing list for WS Resource Access
URL:
Whiteboard:
Keywords: hasProposal
Depends on:
Blocks:
 
Reported: 2009-05-27 03:32 UTC by Geoff Bullen
Modified: 2009-08-18 21:20 UTC (History)
1 user (show)

See Also:


Attachments

Description Geoff Bullen 2009-05-27 03:32:36 UTC
Section 3 states
Once the last element in a sequence has been returned, or the enumeration context has expired, the enumeration context is considered invalid and the result of subsequent operations referencing that context is undefined.

Section 3.2 (request) states
If the enumeration context is not valid, either because it has been replaced in the response to another Pull request, or because it has completed (EndOfSequence has been returned in a Pull response), or because it has been Released, or because it has expired, or because the data source has had to invalidate the context, then the data source SHOULD fail the request, and MAY generate the following fault

Section 3.2 (response) states
Additionally, once this element is returned in a Pull response message, subsequent Pull requests using that enumeration context SHOULD generate a wsen:InvalidEnumerationContext fault message; in any case, they MUST NOT return a valid PullResponse.

This appears to be inconsistent as section 3 states that it is undefined, the first part of section 3.2 states that the server SHOULD fail and MAY return a particular fault, later section 3.2 states that the server SHOULD return this fault and MUST NOT return a valid PullResponse.  

Proposal:
section 3.2 (response) be changed to: MAY generate a wsen:InvalidEnumerationContext message, and delete the in any case, they MUST NOT return a valid PullResponse.
Comment 1 Robert Freund 2009-06-03 05:54:06 UTC
discussed briefly on 2009-06-02, one member asked for more time to consider
Comment 2 Robert Freund 2009-06-09 16:47:03 UTC
Action on Geoff to refine proposal due 6/10
Comment 4 Robert Freund 2009-06-11 22:57:44 UTC
Resolved with comment #3