Bug 8886 – Eventing/Enum - is expiration cause for xxxEnd msg

Bug 8886 - Eventing/Enum - is expiration cause for xxxEnd msg

Summary:

Eventing/Enum - is expiration cause for xxxEnd msg

Status:	CLOSED REMIND

Product:	WS-Resource Access
Component:	Enumeration
Version:	LC
Platform:	PC Windows XP

Importance:	P2 normal
Target Milestone:	---
Assigned To:	Doug Davis
QA Contact:	notifications mailing list for WS Resource Access

URL:
Whiteboard:
Keywords:	hasProposal

Depends on:
Blocks:
	Show dependency tree / graph

Reported:	2010-02-05 21:28 UTC by Doug Davis
Modified:	2010-07-27 20:25 UTC (History)
CC List:	1 user (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.

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