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 6414 - WS-Enum - EOS shouldn't invalidate the context
Summary: WS-Enum - EOS shouldn't invalidate the context
Status: CLOSED WONTFIX
Alias: None
Product: WS-Resource Access
Classification: Unclassified
Component: Enumeration (show other bugs)
Version: FPWD
Hardware: PC Windows XP
: P2 normal
Target Milestone: ---
Assignee: Doug Davis
QA Contact: notifications mailing list for WS Resource Access
URL: http://lists.w3.org/Archives/Public/p...
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-01-14 00:15 UTC by Doug Davis
Modified: 2009-03-12 00:22 UTC (History)
1 user (show)

See Also:

Attachments

Description Doug Davis 2009-01-14 00:15:40 UTC 
When iterating over a dataset the <wsen:EndOfSequence/> element will be 
sent back to the client when the iterator reaches the end of the data. 
This will also invalidate the EnumerationContext - which means that if 
we're iterating over a log file (which might grow) or we want to use some 
advanced cursor feature - we can't.  WS-Enum shouldn't invalidate the 
EnumerationContext so that the client can continue to use it if it wishes.

Proposal:
Remove text in WS-Enum that invalidates the EnumerationContext upon 
reaching the end of the dataset.
Comment 1 Doug Davis 2009-01-16 11:20:46 UTC 
Withdrawn