[Bug 6432] Eventing: Push delivery mode does not work when the subscriber is not addressable

http://www.w3.org/Bugs/Public/show_bug.cgi?id=6432


Doug Davis <dug@us.ibm.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |dug@us.ibm.com




--- Comment #5 from Doug Davis <dug@us.ibm.com>  2009-07-24 14:37:50 ---
New proposal:

(Might be jumping the gun but this is based on the assumption that we
accept the proposal for 6692 that was sent in)

Modify section "2.2 Delivery" with the following (new text in ***):

2.2 Delivery
This specification defines only an asynchronous method of delivery for
notifications from the event source to event sink.  Other methods or
combination of methods may be defined through the use of delivery extensions.

*** start ***
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 subscriber MAY choose to leverage the
[WS-MakeConnection] specification to enable delivery of Notifications to
non-addressable endpoints. This specification defines a SOAP header that SHOULD
be included in the messages to ensure that the receiver will detect and adhere
to the semantics of the WS-MakeConnection specification for any
WS-MakeConnection Anonymous URI used within the message:

<wse:MCSupported mustUndersand="1"/>

An endpoint receiving and accepting a message with this SOAP header MUST adhere
to the semantics of the WS-MakeConnection specification for any EPR that uses
the MakeConnection Anonymous URI in the wsa:Address element. See the
[WS-MakeConnection] specification for more information, and an example, of how
this would work.
*** end ***


-- 
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.

Received on Friday, 24 July 2009 14:37:59 UTC