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

WS-Eventing Subscriber-side state questions

From: Gilbert Pilz <gilbert.pilz@oracle.com>
Date: Wed, 09 Sep 2009 16:57:15 -0700
Message-ID: <4AA840DB.7080301@oracle.com>
To: "public-ws-resource-access@w3.org" <public-ws-resource-access@w3.org>
I've been working on AI 95 and I have a couple questions about the 
Subscribers view of the state of a Subscription under various circumstances.

1.) If I have created a Subscription with a Subscribe/SubscribeResponse 
exchange and I attempt to renew the Subscription by sending a Renew 
message to the Subscription Manager and I receive a UnableToRenew fault, 
what should I consider the state of the Subscription to be, (a) 
unchanged (i.e. same as before the Renew attempt), (b) terminated, (c) 
undetermined?

2.) If I have created a Subscription (blah, blah) and I attempt to 
unsubscribe by sending a Unsubscribe message and I receive a fault 
response (e.g. InvalidMessage), what should I consider the state of the 
Subscription to be, (a) unchanged, (b) terminated, (c) undetermined?

FWIW I think the answer is 'a' in both cases. In general I think 
WS-Eventing needs to be clearer about the effects of various faults on 
the state of the Subscription. For example, I think we need to make it 
clear that any request message that causes the InvalidMessage fault to 
be generated has no effect on the Event Source; it's as if the request 
message were never sent.

- gp




Received on Wednesday, 9 September 2009 23:58:06 GMT

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