[Bug 9613] Eventing: Support WS-Management's persistent subscriptions

http://www.w3.org/Bugs/Public/show_bug.cgi?id=9613


Tom Rutt <tom@coastin.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |tom@coastin.com




--- Comment #2 from Tom Rutt <tom@coastin.com>  2010-05-11 21:40:27 ---
Proposed WG Response to Originator:

WS-RA WG Response to originator of Bug 9613: Eventing: Support WS-Management's
persistent subscriptions

The WS-RA WG considered the WS-Management Last Call comment, 
Logged as Bug 9613.

Persistence is a difficult topic.  For example, we do not understand 
why an event source which can handle persistence of subscriptions 
would not persist all of its subscriptions.

We see this as a quality of service concern, and after due consideration, 
we have decided that ways to accommodate such concerns are domain 
specific and outside the scope of the WS-RA work.

These kind of Quality of service concerns should be dealt with in an 
implementation or domain specific manner.  For example, a management
workstation could be able to determine the kind of event sources it is 
dealing with, and have a table in its own state to know whether each event 
source supports persistence of its subscriptions. 

However, our discussions made us realize that the spec needs a 
clarification regarding the possibility of an event source / subscription 
manager going down before it can send a subscription End message to an 
EndTo epr.

We agreed to close this Bug with the following changes to the WS-Eventing
specification:

Add “, if possible.” to the end of the first paragraph of 4.5 Subscription End

add the following to end of 2nd para in section 4:
“via a SubscriptionEnd message if an EndTo was present in the Subscribe 
message.”

-- 
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.

Received on Tuesday, 11 May 2010 21:40:28 UTC