Hi,
I'm not clear about the dynamic subscriptions, current implementation
will provide 3 options, using WS-Eventing, WS-Notification and user
define messages, how we are going to identify the subscription in the
user define mode ? What happens when a user unsubscribe for a static
subscriptions ? (Remove it or stop sending till the instance up) What
happens when a user unsubscribe where registry is on read only mode ?
With the current model synapse act as the event processing engine and
the event channel, IMO we have to make provision to plug a CEP (like
Esper) to the model as well.
Asanka A.
Ruwan Linton wrote:
Sorry Paul, I was also unable to comment on your last queries.... as
you may know I am traveling. I think the above 2 points that you made
have some interesting value in it. Therefore I would like to keep the
ability to configure the event source and the notification service
sections in the configuration.
As you told, I just started the implementation and you can expect the
initial version soon. For that lets go with the proposed configuration
and I will keep the two elements to configure the notification section
and publishing section.
BTW: I am seeing a test failure in the trunk? Do any one know the
reason for this? Andreas?
(PS: please make sure all tests are passing before commit)
Thanks,
Ruwan
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
