- From: <bugzilla@wiggum.w3.org>
- Date: Fri, 05 Feb 2010 21:28:52 +0000
- To: public-ws-resource-access-notifications@w3.org
http://www.w3.org/Bugs/Public/show_bug.cgi?id=8886
Summary: Eventing/Enum - is expiration cause for xxxEnd msg
Product: WS-Resource Access
Version: LC
Platform: PC
OS/Version: Windows XP
Status: NEW
Severity: normal
Priority: P2
Component: Enumeration
AssignedTo: public-ws-resource-access-notifications@w3.org
ReportedBy: dug@us.ibm.com
QAContact: public-ws-resource-access-notifications@w3.org
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.
--
Configure bugmail: http://www.w3.org/Bugs/Public/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.
You are the assignee for the bug.
Received on Friday, 5 February 2010 21:28:53 UTC