Re: draft 3 of WS-Eventing state tables

Ram,

I notice that you have significantly changed the layout of the table. 
Would you care to share your motivations for doing this?

Also, it seems that a number of details are missing from these tables. 
For example, if you remember Li's and my discussion on this, it is 
possible to receive a Notification for a Subscription prior to receiving 
the wse:SubscribeResponse. This isn't indicated anywhere in your tables 
but it seems like one those things state tables are good at highlighting 
and that need to be pointed out.

Also, per our conversations on the concall of 10/20, there needs to an 
indication that the UnknownSubscription fault code results in a 
different state transition than other fault codes. For example, if you 
sent a GetStatus request and get back an UnknownSubscription fault, you 
need to go to the [End] state whereas, if you get a generic SOAP fault, 
you should assume the Subscription is still live and go back to the 
[Created]/[Active] state.

- gp

On 10/27/2009 9:23 AM, Ram Jeyaraman wrote:
>
> Based on conversations during the October F2F in Hursley, England, I 
> suggest changes to the version of WS-Eventing state tables produced by 
> Gil. A revised version of the WS-Eventing state tables is attached for 
> review. Thanks.
>
>  
>
> *From:* public-ws-resource-access-request@w3.org 
> [mailto:public-ws-resource-access-request@w3.org] *On Behalf Of 
> *Gilbert Pilz
> *Sent:* Friday, September 11, 2009 5:30 PM
> *To:* public-ws-resource-access@w3.org
> *Subject:* draft 3 of WS-Eventing state tables
>
>  
>
> Attached is draft 3 of the state tables for WS-Eventing. I've added an 
> "Expiration" event to the Event Sinks table as well as cleaned up some 
> missing values for the "Subscription End" event.
>
> - gp
>