- From: Li, Li (Li) <lli5@avaya.com>
- Date: Tue, 29 Sep 2009 18:03:23 -0400
- To: <public-ws-resource-access@w3.org>
- Cc: "Chou, Wu (Wu)" <wuchou@avaya.com>
Katy, I have a minor problem with using EventSourceUnableToProcess as the catch-all fault for the getstatus/renew/unsubscribe messages, as in your proposal [1]: 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. I think EventSourceUnableToProcess is ok for the subscribe message as it is sent to the Event Source. But using it for other messages seems inconsistent with our architecture that these other messages are sent to the Subscription Manager, not the Event Source. Would a SubscriptionManagerUnableToProcess be more appropriate? Thanks. Li [1] http://lists.w3.org/Archives/Public/public-ws-resource-access/2009Sep/00 52.html
Received on Tuesday, 29 September 2009 22:04:04 UTC