This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.
Section 2.2 says: -- When the wse:NotifyTo element is used within the Delivery element it specifies the endpoint to which Notifications are sent. For delivery to addressable endpoints this is sufficient. However, for non-addressable endpoints some additional mechanisms are needed. A subscription manager MAY choose to support mechanisms, such as the [WS-MakeConnection] specification, to enable delivery of Notifications to non-addressable endpoints. -- which is fine for NotifyTo but leaves people in the dark about EndTo. Proposal: Add to the end of the above text something like: -- Likewise, the wse:EndTo element MAY make use of the WS-MakeConnection Anonymous URI to enable delivery of the SubscriptionEnd message from the Subscription Manager. -- The last bit is the critical piece - we don't really need to tell people about using MC in any EPR, however, we _do_ need to make it clear where the MC message needs to go. In this case, like with notifications, we need to tell people that the Subscription Manager is the place to send the MC msg.
Doug, I have some questions: 1) while in theory the EndTo EPR can be non-addressable, i wonder what is the use case for it. Since SubscriptionEnd is just one message sent once by the subscription manager, it seems an overkill to use MC to poll it. Can we just mandate that the EPR, if present, be addressable to simplify a lot of things? 2) If the subscriber is willing to MC poll that one event, why can't it poll the subscription with GetStatus? Both methods will tell if the subscription is active. 3) you mentioned that current ws-e spec says MC should be sent to the subscription manager for regular notifications, but i couldn't find where the statement is. thanks. Li
Li, as always this is an impl choice but if people do choose to do it then we need to make it clear what people should do - otherwise it'll be an interop issue. As for NotifyTo, the spec says: A subscription manager MAY choose to support mechanisms, such as the [WS-MakeConnection] specification, to enable delivery of notifications to non-addressable endpoints.
Latest proposal: http://lists.w3.org/Archives/Public/public-ws-resource-access/2009Dec/0025.html
resolved with proposal: add "and the SubscriptionEnd message" to the MC text per http://lists.w3.org/Archives/Public/public-ws-resource-access/2009Dec/0025.html but do not include the Note: