RE: [Pub-Sub-Task] initial half-baked proposal from me

In my mind Sanjiva's proposal is a good idea. However, I wonder if
this new model of events producer/consumer/filter/transport/security
should not be captured in a separate specification before making any
changes to WSDL.

I believe that some work has already been done by the Internet
community in that space a long time ago. We could re-use this to come
up with a new spec. (say WS-Event) defining events in a WS world and
proposed some WSDL changes if necessary.

Niko

Sedukhin, Igor writes:
 > 
 > +1 to Sanjiva's proposal at the top-level.
 > There is one small "but" from me. I believe that passing service reference is not a mandatory part of the subscription message defined at the top level, but rather a business of the binding.
 > 
 > In my view binding of an event (notification) needs to define:
 >  * for a "producer role"
 >   - subscription/ack sequence and message layout with "consumer" reference (and/or binding) place in it
 >   - subscription update/removal sequence, frequency and message layout
 >  * for a "consumer role"
 >   - notification/ack sequence and message layout
 >   - keep-alive/solicit-update notification acceptance, sequence, message layout and optimal frequency
 > 
 > 
 > -- Igor Sedukhin .. (igor.sedukhin@ca.com)
 > -- (631) 342-4325 .. 1 CA Plaza, Islandia, NY 11788
 > 

-- 
Nicolas Catania

Web Services Management Operation
HP Openview Division
+1 408 447-4564
nicolas_catania@hp.com

Received on Monday, 4 November 2002 13:35:38 UTC