RE: Issue 8164: proposal

Ø  A subscription manager MAY choose to support mechanisms, such as the [WS-MakeConnection] specification, to enable delivery of notifications and the SubscriptionEnd message to non-addressable endpoints.

This looks good.


Ø  Note: as an optimization, a subscriber SHOULD consider using the same WS-MakeConnection Anonymous URI in both the NotifyTo and EndTo EPRs to allow the same MakeConnection message to be used to transmit either notifications or a SubscriptionEnd message.

Since there are valid situations that may require using different WS-MakeConnection Anonymous URIs in the NotifyTo and EndTo EPRs, the specification need not restrict the usage. Hence, I suggest deleting this sentence.

Thanks.

From: public-ws-resource-access-request@w3.org [mailto:public-ws-resource-access-request@w3.org] On Behalf Of Doug Davis
Sent: Tuesday, December 08, 2009 10:08 PM
To: public-ws-resource-access@w3.org
Subject: Issue 8164: proposal


(resending w/o extra stuff)

Proposal:
change:
A subscription manager MAY choose to support mechanisms, such as the [WS-MakeConnection] specification, to enable delivery of notifications to non-addressable endpoints.
to:
A subscription manager MAY choose to support mechanisms, such as the [WS-MakeConnection] specification, to enable delivery of notifications and the SubscriptionEnd message to non-addressable endpoints. Note: as an optimization, a subscriber SHOULD consider using the same WS-MakeConnection Anonymous URI in both the NotifyTo and EndTo EPRs to allow the same MakeConnection message to be used to transmit either notifications or a SubscriptionEnd message.

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