- From: <bugzilla@jessica.w3.org>
- Date: Tue, 11 May 2010 15:03:45 +0000
- To: public-ws-resource-access-notifications@w3.org
http://www.w3.org/Bugs/Public/show_bug.cgi?id=9611
Li Li <lli5@avaya.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |lli5@avaya.com
--- Comment #1 from Li Li <lli5@avaya.com> 2010-05-11 15:03:43 ---
Gil,
Some comments on the proposal points:
On 1:
This would rule out event source using Notification WSDL to advertise event
structures as defined in Appendix A.2.
On 2:
It seems that 1 and 2 can be covered by the current Wrapped WSDL defined
Appendix D. Assume the event structures (event-i) are advertised according to
Appendix A, then batched events can be delivered as a sequence of child
elements of wse:Notify:
<wse:Notify>
<ns1:event-1>...</ns1:event-1>
<ns2:event-2>...</ns2:event-2>
...
</wse:Notify>
Therefore, current WS-E may support 1 and 2 without change by wrapped delivery
format.
On 3:
If the batched delivery can be handled by wrapped format, then the subscriber
can use the standard Wrapped URI in the subscribe request. Moreover,
introducing new batched delivery format URI requires to define the
subscriber/event source behavior associated with it. However, we think the
behavior of event batching is highly service dependent, for example, deadline
based or frequency based batching rules, etc. Therefore, it seem better to
leave it to the extension services.
Wu, Li
--
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 Tuesday, 11 May 2010 15:03:46 UTC