W3C home > Mailing lists > Public > public-ws-resource-access@w3.org > September 2009

Issue 7554: Eventing - Unsubscribe Fault Message (action item 103)

From: Katy Warr <katy_warr@uk.ibm.com>
Date: Thu, 17 Sep 2009 17:48:01 +0100
To: public-ws-resource-access@w3.org
Message-ID: <OFAC7F5AAF.AC7B4DAB-ON80257634.005ABADF-80257634.005C497F@uk.ibm.com>
Following discussions from Tuesday's call, here's a proposed fix for 
http://www.w3.org/Bugs/Public/show_bug.cgi?id=7554 action item 103 
http://www.w3.org/2002/ws/ra/tracker/actions/103

Please note:  Li li added a comment to this issue here 
http://www.w3.org/Bugs/Public/show_bug.cgi?id=7554#c1 suggesting that we 
should have an UnableToXXX fault for each of Subscribe, Renew, GetStatus, 
Unsubscribe.  Currently, Subscribe uses EventSourceUnableToProcess for 
this purpose; Renew uses UnableToRenew; Unsubscribe and GetStatus don't 
have an equivalent fault.  This proposal suggests that they all share the 
EventSourceUnableToProcess fault to indicate a general failure to process 
the request.

This proposal is based on the proposal for 7553 being accepted (and may 
need to change if it is not): 

1) Add text to 4.4 Unsubscribe:
"If the event source is unable to perform the Unsubscribe because the 
subscription is not valid, the request MUST fail and the subscription 
manager MUST generate a wse:InvalidSubscription fault.  If the 
subscription is valid, but the event source chooses not to perform the 
Unsubscribe, the event source MUST generate a 
wse:EventSourceUnableToProocess fault."

2) Change the text of the EventSourceUnableToProcess fault so that it is 
not specific to Subscribe:
"This fault is generated when the event source is not capable of 
fulfilling a request for local reasons unrelated to the specific request."

3) Remove the unableToRenew fault and reuse the EventSourceUnableToProcess 
for consistent approach with subscribe and unsubscribe.
Change text in 4.2 Renew to:
"If the subscription manager chooses not to renew this subscription, the 
request MUST fail, and the subscription manager MUST generate a 
wse:EventSourceUnableToProcess fault indicating that the renewal was not 
accepted. "

4) Change the text in 4.3  GetStatus to add EventSourceUnableToProcess
"If the event source is unable to perform the GetStatus because the 
subscription is not valid, the request MUST fail and the subscription 
manager MUST generate a wse:InvalidSubscription fault.  If the 
subscription is valid, but the event source chooses not to perform the 
GetStatus, the event source MUST generate a 
wse:EventSourceUnableToProocess fault."





Unless stated otherwise above:
IBM United Kingdom Limited - Registered in England and Wales with number 
741598. 
Registered office: PO Box 41, North Harbour, Portsmouth, Hampshire PO6 3AU
Received on Thursday, 17 September 2009 16:49:07 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Saturday, 18 December 2010 18:18:13 GMT