- From: <bugzilla@jessica.w3.org>
- Date: Wed, 28 Apr 2010 22:09:39 +0000
- To: public-ws-resource-access-notifications@w3.org
http://www.w3.org/Bugs/Public/show_bug.cgi?id=9611
Summary: Support WS-Management's Batched delivery format
Product: WS-Resource Access
Version: LC
Platform: All
OS/Version: All
Status: NEW
Severity: enhancement
Priority: P2
Component: Eventing
AssignedTo: public-ws-resource-access-notifications@w3.org
ReportedBy: gilbert.pilz@oracle.com
QAContact: public-ws-resource-access-notifications@w3.org
WS-Management v1.1 [1] Section 10.2.9.4 defines a “Batched Delivery Mode” in
which multiple events are bundled into a single notification. WS-Man notes:
"Batching events is an effective way to minimize event traffic from a
high-volume event source without sacrificing event timeliness."
It is the opinion of the WS-Man WG that this feature is sufficiently general as
to warrant inclusion in the base specification. The WS-Man WG requests that the
WS-RA WG incorporate this extension as an optional feature of WS-Eventing.
[1] http://www.dmtf.org/standards/published_documents/DSP0226_1.1.pdf
---
Proposal:
1. Define a new wrapper element that contains a sequence of wse:EventType.
2. Define a new abstract WSDL, similar to that in Appendix D of WS-Eventing,
that describes the interface that the Event Sink must implement to receive
Batched Notifications. It should define a message with the type described in
(1) and a one-way operation that accepts this message as its input. This
operation should be assigned a wsam:Action of
“http://www.w3.org/2002/ws/ra/edcopies/ws-evt/BatchedSinkPortType/NotifyEvent”.
3. Define a new delivery format with the URI
“http://www.w3.org/2002/ws/ra/edcopies/ws-evt/DeliveryFormats/Batched” that
indicates the use of the above.
--
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 Wednesday, 28 April 2010 22:10:21 UTC