Have a continuation parked at a name that is a subscription. It is read-only. Requests for listening at name should be pooled with an external service.
After continuation feature implemented, we could get rid of LFDAN api
Most applications want the watcher continuation to fire after finalization. There are some riskier apps that are willing to follow unfinalized data
Triggering the watcher happens before finalization, but publication can’t happen until there is finalization
Continuation goes in RSpace so it can be persisted
Question: Who pays for executing the continuation?
Question: How do I get the data back? Paramatize the continuation via http?
How do I know the name I’m listening for?
You can only LAN after the name exists and after the the subscription is set up
REQUIREMENT: observe data at a particular name
QUESTION: If we have a callback, the callback has to be executed. In a distributed system it’s hard to ensure the callback happens once and only once. Who owns the callback?
QUESTION: How do we observe changes in values in the channel?
The events themselves are the trigger for the watcher continuation. At the movement there is an event to update the name, that is the moment you trigger the watcher to see if there is any finalization.
Concern RSpace can’t support this as currently operating
IDEA expose an event log that users can subscribe to (Artur)