- From: Doug Davis <dug@us.ibm.com>
- Date: Tue, 14 Jun 2011 15:16:20 -0400
- To: David Gregorczyk <gregorczyk@itm.uni-luebeck.de>
- Cc: public-ws-resource-access@w3.org
- Message-ID: <OFB8396287.C6812AC6-ON852578AF.006999CC-852578AF.0069DE86@us.ibm.com>
David, If I'm understanding your scenario, yes you can put policy assertions under the wse:NotificationPolicy element to indicate which type of transport mechanisms can be used to send Notifications. So, for example, if you put the SOAP11 or SOAP12 assertion in there then that will indicate that which version of SOAP will be used to send the Notifications. In your case, if someone were to define policy assertions to indicate the use of TCP or UDP then they can be placed in there too. thanks -Doug ______________________________________________________ STSM | Standards Architect | IBM Software Group (919) 254-6905 | IBM 444-6905 | dug@us.ibm.com The more I'm around some people, the more I like my dog. David Gregorczyk <gregorczyk@itm.uni-luebeck.de> Sent by: public-ws-resource-access-request@w3.org 06/14/2011 10:29 AM To public-ws-resource-access@w3.org cc Subject wse:NotificationPolicy Hi folks, today I've studied WS-Eventing and ask me a question about wse:NotificationPolicy. What is the concrete sense / usage of this element or respectively its children? I think, I didn't understand the description within the WS-Eventing report correctly. My intention is to find an adequate place to advertise an alternative notification transmission binding (e.g. TCP/UDP/HTTP/COAP) and assumed wse:NotificationPolicy. If this wouldn't be, where else could be an adequate place for it? Best, David Gregorczyk
Received on Tuesday, 14 June 2011 19:17:10 UTC