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 8886 - Eventing/Enum - is expiration cause for xxxEnd msg
Summary: Eventing/Enum - is expiration cause for xxxEnd msg
Status: CLOSED REMIND
Alias: None
Product: WS-Resource Access
Classification: Unclassified
Component: Enumeration (show other bugs)
Version: LC
Hardware: PC Windows XP
: P2 normal
Target Milestone: ---
Assignee: Doug Davis
QA Contact: notifications mailing list for WS Resource Access
URL:
Whiteboard:
Keywords: hasProposal
Depends on:
Blocks:
 
Reported: 2010-02-05 21:28 UTC by Doug Davis
Modified: 2010-07-27 20:25 UTC (History)
1 user (show)

See Also:

Attachments

Description Doug Davis 2010-02-05 21:28:51 UTC 
Eventing and Enum aren't clear on whether a xxxEnd messages is supposed to 
be sent when the subscription/enum-context expires.  Basically, is
an expiration an "unexpected" occurrence?  I think the answer is "no" but
we should make it clear.

Proposal:
In the first paragraph of eventing/enum xxxEnd section add:

Note, a (subscription|enumeration context) expiring is not considered to be an unexpected termination, therefore a xxxEnd message MUST NOT be sent in this case.
Comment 1 Ram Jeyaraman 2010-03-16 20:45:16 UTC 
Note, a (subscription|enumeration context) expiring as expected is not considered to be an unexpected termination, therefore a xxxEnd message MUST NOT be sent in this case.
Comment 2 Robert Freund 2010-03-16 20:47:01 UTC 
resolved with comment #1