8274 2009-11-13 06:30:01 +0000 Eventing: interoperability of non-addressable event sinks 2009-11-19 16:10:53 +0000 1 1 1 Unclassified WS-Resource Access Eventing FPWD All All CLOSED WONTFIX hasProposal P2 normal --- 1 gilbert.pilz public-ws-resource-access-notifications public-ws-resource-access-notifications oldest_to_newest 29538 0 gilbert.pilz 2009-11-13 06:30:01 +0000 Section 2.2 "Delivery" contains the following paragraph: "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. See the [WS-MakeConnection] specification for more information, and an example, of how this would work." The "MAY choose to support" clause in the above means that the set of event source implementations that support non-addressable sinks will be fractured into those that support WS-MakeConnection and those that support some other polling mechanism. The has obvious impacts on interoperability. Proposal: rephrase the above to "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. Event sources and subscription managers that support non-addressable event sinks MUST support the [WS-MakeConnection] specification."