7554 2009-09-09 16:03:31 +0000 Eventing: Unsubscribe Fault 2009-10-12 21:19:12 +0000 1 1 1 Unclassified WS-Resource Access Eventing FPWD PC Windows XP CLOSED REMIND hasProposal P2 normal --- 1 nolanpt katy_warr dug lli5 public-ws-resource-access-notifications oldest_to_newest 26985 0 nolanpt 2009-09-09 16:03:31 +0000 Section 4.4 Unsubscribe, describes the message to be returned if an Unsubscribe message is accepted. However it does not mention what to return if the Unsubscribe request is not accepted. Proposal: Add a new fault to section 6. 6.15 UnableToUnsubscribe This fault is generated when an unsubscribe request has failed. [Code] s12:Sender [Subcode] wse:UnableToUnsubscribe [Reason] The Unsubscribe request has failed [Detail] none 27243 1 lli5 2009-09-16 14:50:24 +0000 just record my comment before forgetting it. Agree there should be a fault message for Unsubscribe, for example, when the subscription does not exist. However, in that case, the fault should be InvalidSubscription as proposed in Issue 7553 [1]. If we create an UnableToUnsubscribe fault, it would allow a service to fail a request with any reason beyond the listed ones. If that is the case, should we also add UnableToXXX to each request as well? Thanks. [1] http://www.w3.org/Bugs/Public/show_bug.cgi?id=7553 27885 2 lli5 2009-09-29 18:50:05 +0000 Latest proposal at http://lists.w3.org/Archives/Public/public-ws-resource-access/2009Sep/0052.html. 28022 3 bob 2009-10-02 14:28:48 +0000 consolidated with 7553 Resolution to 7553 will also resolve 7554