- From: Doug Davis <dug@us.ibm.com>
- Date: Thu, 28 Jan 2010 00:55:11 -0500
- To: public-ws-resource-access@w3.org
Received on Thursday, 28 January 2010 05:55:50 UTC
My suggested edits to the state tables for ws-eventing: Sink Table 1 - RenewResponse/End: leave blank Source Table: 1 - SubscribeRequest/Active: leave blank 2 - SubscribeRequest/End: leave blank 3 - RenewRequest->UnsubscribeRequest/Idel: leave blank (3 boxes) Suggestions for the ws-enum state tables: Consumer Table: 1 - any reason there isn't a Pull [app] trigger? 2 - RenewResponse/End: leave blank 3 - InvalidEnumerationContext/End: leave blank - can this trigger actually happen? isn't it part of one of the other faults listed above? Data Source Table: 1 - EnumerateRequest/Action & EnumerateRequest/End: leave blank 2 - all boxes in Idle column (except first): leave blank 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.
Received on Thursday, 28 January 2010 05:55:50 UTC