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

[Bug 7554] Eventing: Unsubscribe Fault

From: <bugzilla@wiggum.w3.org>
Date: Wed, 16 Sep 2009 14:50:24 +0000
To: public-ws-resource-access-notifications@w3.org
Message-Id: <E1Mnvpw-0001bG-KH@wiggum.w3.org>
http://www.w3.org/Bugs/Public/show_bug.cgi?id=7554


Li Li <lli5@avaya.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |lli5@avaya.com




--- Comment #1 from Li Li <lli5@avaya.com>  2009-09-16 14:50:24 ---
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 


-- 
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 Wednesday, 16 September 2009 14:50:33 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Wednesday, 16 September 2009 14:50:34 GMT