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 6428 - Eventing: Separate Event Delivery Mode and Format
Summary: Eventing: Separate Event Delivery Mode and Format
Status: CLOSED REMIND
Alias: None
Product: WS-Resource Access
Classification: Unclassified
Component: Eventing (show other bugs)
Version: FPWD
Hardware: PC Windows 2000
: P2 normal
Target Milestone: ---
Assignee: Li Li
QA Contact: notifications mailing list for WS Resource Access
URL:
Whiteboard:
Keywords: migrationPathNeeded, needsAction
Depends on: 6429
Blocks:
  Show dependency tree / graph
 
Reported: 2009-01-14 17:48 UTC by Li Li
Modified: 2009-04-21 21:32 UTC (History)
2 users (show)

See Also:

Attachments

Description Li Li 2009-01-14 17:48:58 UTC 
Section 1.2 of WS-Eventing specifies an attribute call Delivery Mode. This attribute is used to indicate both event delivery mode (push or poll) and event delivery format (wrapped or unwrapped). Using one attribute for 4 combinations is not extensible. It prevents combining existing modes or formats with new ones. We propose to separate mode and format by adding a new attribute Format:

wse:Subcribe/wse:Delivery/@Format="http://schemas.xmlsoap.org/ws/2004/08/eventing/DeliveryModes/Unwrap"
Comment 1 Robert Freund 2009-01-15 23:54:29 UTC 
2009-01-15: considered, further discussion to the list
Comment 3 Robert Freund 2009-02-18 11:46:02 UTC 
CVonsidered 2009-02-17, 6429 is thought to be a blocking issue
Comment 4 Robert Freund 2009-03-10 18:49:49 UTC 
Action-34
Comment 5 Robert Freund 2009-03-11 09:36:21 UTC 
Action-34 results
New proposal at http://lists.w3.org/Archives/Public/public-ws-resource-access/2009Mar/0053.html
Comment 6 Robert Freund 2009-03-11 18:13:03 UTC 
2009-03-11 Resolved with proposal in Comment # 5
MigrationPathNeeded
Comment 7 Li Li 2009-03-17 15:35:08 UTC 
Since the format is extensible and people could define a format that includes batching we should modify the definition of Push Mode from: 

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

to:

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

by deleting the word "individual."
Comment 8 Doug Davis 2009-03-17 23:36:32 UTC 
Done - including comment #7