- From: Doug Davis <dug@us.ibm.com>
- Date: Tue, 6 Apr 2010 00:07:56 -0400
- To: Gilbert Pilz <gilbert.pilz@oracle.com>
- Cc: "public-ws-resource-access@w3.org" <public-ws-resource-access@w3.org>
- Message-ID: <OF0DE11010.4B31910E-ON852576FD.001675D3-852576FD.0016B36F@us.ibm.com>
Looks good to me. 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. Gilbert Pilz <gilbert.pilz@oracle.com> Sent by: public-ws-resource-access-request@w3.org 04/05/2010 02:29 PM To "public-ws-resource-access@w3.org" <public-ws-resource-access@w3.org> cc Subject proposal for issue 8832 Attached is a proposal for issue 8832. As suggested on a recent call, this proposal copies one of the recent changes to WS-Enumeration by adding the following text to section 4: A subscription can become invalid for any reason including: 1. Subscription deleted (via Unsubscribe) 2. Subscription expired 3. Subscription ended (via SubscriptionEnd) In addition, the Event Source/Subscription Manager MAY cancel a subscription at any time, as necessary. When processing a Renew, GetStatus or Unsubscribe operation, a Subscription Manager MUST generate an wse:UnknownSubscription fault if it determines that the subscription is invalid. Once a Subscriber determines that a subscription is invalid, it MUST NOT issue any more WS-Eventing request messages using that subscription. I've attached an edited HTML version along with a PDF that highlights the changes. - gp[attachment "8832.zip" deleted by Doug Davis/Raleigh/IBM]
Received on Tuesday, 6 April 2010 04:09:08 UTC