W3C home > Mailing lists > Public > public-ws-resource-access@w3.org > April 2009

RE: [Bug 6692] New: Remove Mode from the specification

From: Chou, Wu (Wu) <wuchou@avaya.com>
Date: Fri, 3 Apr 2009 11:31:07 -0400
Message-ID: <F81BDFA28AE48D4793E253362D1F7A740112AB14@300813ANEX2.global.avaya.com>
To: <public-ws-resource-access@w3.org>
Cc: "Doug Davis" <dug@us.ibm.com>, "Bob Freund" <bob.freund@hitachisoftware.com>, "Li, Li (Li)" <lli5@avaya.com>
Mode attribute in WS-E is to specify the additional required event
delivery behavior or required application/business logic extensions that
the event source must understand/support before being allowed to accept
the event subscription.
My understanding is: "push_event_thru_proxy" is for all events delivery
from the Subscribe. As such, it covers SubscriptionEnd event. The Mode
attribute also allows to specify fine grained application logic to
control the event delivery.  If you want, more fine grained event
delivery logic/procedure can be easily added to Mode attribute to
control the event delivery, e.g.
"push_thru_proxy_for_non_subscriptionend_event", etc. 
Mode attribute in WS-E provides a standard extension point to add
application specific logic and behavior to event delivery, so that it
can enforce the required procedure/logic for business applications when
using WS-Eventing for event delivery.
- Wu Chou.
 > since its too easy for things to get lost in these long messages, let
focus on one particular aspect of this.  
>Surely the idea of using a proxy 
for sending messages is not WS-Eventing specific.  How do you support 
sending any other asynchronous message (non-NotifyTo messages) thru a 
>Need a clarification on th, e.g. a general question, a question for
WS-E or a question for WS-E plus Mode.
>For example, the SubscriptionEnd message.


Wu Chou, IEEE Fellow, Ph.D. | Director |Dialogue System Research | AVAYA
| 233 Mt. Airy Road| Rm. 2D48 | Basking Ridge, NJ 07920 | Voice/Fax:
908-696-5198 / 908-696-5401 | wuchou@avaya.com
Received on Friday, 3 April 2009 15:32:01 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 20:34:48 UTC