- From: <bugzilla@jessica.w3.org>
- Date: Wed, 28 Apr 2010 22:19:07 +0000
- To: public-ws-resource-access-notifications@w3.org
http://www.w3.org/Bugs/Public/show_bug.cgi?id=9613 Summary: Support WS-Management's persistent subscriptions Product: WS-Resource Access Version: LC Platform: All OS/Version: All Status: NEW Severity: enhancement Priority: P2 Component: Eventing AssignedTo: public-ws-resource-access-notifications@w3.org ReportedBy: gilbert.pilz@oracle.com QAContact: public-ws-resource-access-notifications@w3.org The WS-Man WG has identified the need for “persistent subscriptions” in WS-Eventing. A “persistent subscription” is a subscription that is guaranteed (by the Event Source) to survive such occurrences as the shutdown/restart of the Event Source's container, the shutdown/restart of the Event Source's VM, or the reboot of the device hosting the Event Source. Although any Event Source is allowed to provide such a quality of service in the current specification, the important aspect of this feature is the Subscribers knowledge of this guarantee. It is the opinion of the WS-Man WG that this feature is sufficiently general as to warrant inclusion in the base specification. --- Proposal: 1. Add an optional element to the wse:Subscribe element (e.g. “wse:Persistent”) that indicates that the Subscriber is requesting a persistent subscription. 2. Create a new fault that MUST be generated by the Event Source if that Event Source is unable/unwilling to create a persistent subscription in the face of a request to do so. 3. Add a parameter to the wse:EventSource assertion that indicates the endpoints ability to create persistent subscriptions. 4. Define a mechanism to allow a client to specify whether the request should be performed with or without the use of this feature in a way similar to the way mustUnderstand works. [1] http://www.dmtf.org/standards/published_documents/DSP0226_1.1.pdf -- 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 Wednesday, 28 April 2010 22:19:49 UTC