W3C home > Mailing lists > Public > public-ws-resource-access-notifications@w3.org > November 2009

[Bug 8164] New: Eventing: delivery of SubscriptionEnd to non-addressable endpoint

From: <bugzilla@wiggum.w3.org>
Date: Tue, 03 Nov 2009 20:39:59 +0000
To: public-ws-resource-access-notifications@w3.org
Message-ID: <bug-8164-2780@http.www.w3.org/Bugs/Public/>
http://www.w3.org/Bugs/Public/show_bug.cgi?id=8164

           Summary: Eventing: delivery of SubscriptionEnd to non-addressable
                    endpoint
           Product: WS-Resource Access
           Version: FPWD
          Platform: PC
        OS/Version: Windows XP
            Status: NEW
          Severity: normal
          Priority: P2
         Component: Eventing
        AssignedTo: public-ws-resource-access-notifications@w3.org
        ReportedBy: dug@us.ibm.com
         QAContact: public-ws-resource-access-notifications@w3.org


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.


-- 
Configure bugmail: http://www.w3.org/Bugs/Public/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.
You are the assignee for the bug.
Received on Tuesday, 3 November 2009 20:40:00 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 21:06:36 UTC