RE: [wsn] Subscribe and GetCurrentMessage

["Patil, Sanjay" <sanjay.patil@sap.com>]

Title: Message

 

Snapshot/update scenario sounds like a useful application of WS-BaseNotification, but I don't think we should build support for snapshot/update in WS-BaseNotification itself.

 

When it comes to actually defining support for snapshot/update, I guess we will have to solve issues such as - how to define the snapshot, and how to define the update. And in that case you might as well use WS-RF, right?

 

Thanks,

Sanjay

-----Original Message-----
From: David Hull [mailto:dmh@tibco.com]
Sent: Tuesday, Nov 23, 2004 13:43 PM
Cc: wsn@lists.oasis-open.org
Subject: Re: [wsn] Subscribe and GetCurrentMessage

Steve Graham wrote:

David Hull <dmh@tibco.com> wrote on 11/22/2004 04:48:34 PM:

> One useful pub/sub paradigm involves the concept of notifications as updates to
> some collection of state.
Indeed, this is what WSRF-Resource Properties suggests.

> In such cases, it is useful to be able to take a
> snapshot of the state, then be notified of updates to that state.
Agreed.  GetResourcePropertyDocument, followed by a subscribe operation specifying
which Resource properties (bits of state) the consumer should receive value change
notifications.

Minus whatever changes happened between the get and the subscribe.  Or plus whatever changes happened between the subscribe and the get.  In any case, we want to be able to cover snapshot/update scenarios where the state is not presented as a WS-Resource.  Or at least I would like that.