RE: Enumeration state tables

Similar comments for this one:
- add an "End" state to both
- use "InvalidEnumContext" fault instead of "send appropriate fault"
- have xxxResponse be a trigger on the client's table (use Gil's triggers)

thanks
-Doug
______________________________________________________
STSM |  Standards Architect  |  IBM Software Group
(919) 254-6905  |  IBM 444-6905  |  dug@us.ibm.com
The more I'm around some people, the more I like my dog.



Ram Jeyaraman <Ram.Jeyaraman@microsoft.com> 
Sent by: public-ws-resource-access-request@w3.org
10/27/2009 02:01 PM

To
Gilbert Pilz <gilbert.pilz@oracle.com>, "public-ws-resource-access@w3.org" 
<public-ws-resource-access@w3.org>
cc

Subject
RE: Enumeration state tables






I have attached version 2 of WS-Enumeration state tables based on the 
prior face-to-face conversations. I suggest adding this as a non-normative 
/ information text to the appendix section. 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 4:31 PM
To: public-ws-resource-access@w3.org
Subject: Enumeration state tables
 
Attached is the first draft of the state tables for WS-Enumeration. 
Overall this was pretty straightforward. The one thing I'm not sure about 
is, when the Consumer is in the "Releasing" state (having sent a 
wsen:Release request) and it receives a fault that is not 
wsen:InvalidEnumerationContext it seems that the Consumer has no choice 
but to assume the request wasn't processed and the Enumeration is still in 
the "Created" state.

While working on these state tables it occurred to me that the issues 
around expiration representation and expiration negotiation that we are 
discussing for WS-Eventing are also issues for WS-Enumeration.

- gp[attachment "Enumeration-State-Tables-v2.doc" deleted by Doug 
Davis/Raleigh/IBM]