This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.

Bug 6692 - WS-Eventing: Remove Mode from the specification
Summary: WS-Eventing: Remove Mode from the specification
Alias: None
Product: WS-Resource Access
Classification: Unclassified
Component: Eventing (show other bugs)
Version: FPWD
Hardware: PC All
: P2 major
Target Milestone: ---
Assignee: David Snelling
QA Contact: notifications mailing list for WS Resource Access
Keywords: hasProposal
Depends on:
Blocks: 6432
  Show dependency treegraph
Reported: 2009-03-12 15:37 UTC by David Snelling
Modified: 2009-09-16 08:12 UTC (History)
3 users (show)

See Also:


Description David Snelling 2009-03-12 15:37:27 UTC
The concept of Mode is redundant in the current version of the specification. All events can be thought of as being delivered. There is no actual definition of "Push Mode" and no other recommended modes. We even have a MakeConnection strategy to allow clients behind NATs to fetch events. Likewise, strategies for complex queuing and distribution are supportable without adding additional modes and are outside the scope of this specification.

Proposal: Remove /s:Envelope/s:Body/*/wse:Delivery/@Mode from the specification and all references to Push Mode. A simple explanation of the delivery idea and a pointer to some of the techniques available will be needed.
Comment 1 Li Li 2009-03-20 13:52:57 UTC
Definition of "Push Mode" is in section 3.3:

Push Mode 
A delivery mechanism where the source sends event messages to the sink as individual, unsolicited, asynchronous SOAP messages. 

Please also see for a proposed change.
Comment 2 Robert Freund 2009-03-24 21:33:20 UTC
discussed at length on 2009-03-24
Comment 3 Robert Freund 2009-03-24 21:45:19 UTC
dependency not agreed at 2009-03-24 meeting
Comment 4 Asir V Selvasingh 2009-04-02 05:33:49 UTC
A description of why delivery mode is needed can be found at:
Comment 5 Robert Freund 2009-04-28 21:23:43 UTC
Comment 6 Robert Freund 2009-06-10 23:17:06 UTC
directional decision achieved
Mode attribute is removed
replaced with a collection of QNames
extension elements scoped to the children of their parent
extension elements put in the "right" place"
delivery or stamp or some-such wrapper to contain extensions and parameters
delivery tentatively and roughly defined as "the collection of rules and parameters for the conveyance of notification messages from source to sink" (which may need more work)
Agreed that the notion of delivery will be maintained and represented by the above wrapper
agreed that future work is needed to tighten up faulting
agreed that future work is needed for subscribe response
At least one member feels that future work might be needed to scope extensions to EndTo.
In any case the mode attribute has been replaced with another mechanism
(action 70 on Geoff)
Comment 7 Robert Freund 2009-06-30 11:16:40 UTC
interim proposal at
Comment 8 Doug Davis 2009-06-30 20:13:16 UTC
And another proposal:
Comment 10 Robert Freund 2009-07-29 14:58:47 UTC
Proposal in comment 9 accepted with the following amendments:
In the sentences:
"The absence of any extensions to the wse:Delivery or wse:NotifyTo elements indicates that notifications should be asynchronously sent as SOAP messages to the endpoint described in lines (21-28). "
"When present this element indicates that notifications MUST be asynchronously sent to the EndpointReference identified by this element."
delete teh word "asynchronously"

change the sentence:
"This specification defines only an asynchronous method of delivery for notifications from the event source to event sink."
"This specification defines a method for transmitting notifications from the event source to the event sink through the use of thew se:NotifyTo element."