Hi
----- Original Message -----
> 3) Would you expect any component generating notifications to
use a 'client
> api' or is direct publishing of the NotificationMessage a valid use case?
>
>
Not sure if I get the "client api" use case, if you can add an example I can
check if the current architecture supports that use case.
At the moment, the idea is that the plugin should listen from the bus, but
you can create an alternative notifications implementation without having
that dependency from the bus (i.e. some thirdparty likes metrics and alerts
components and they want to hard integrate them into other code, so they
won't use the bus but the API defined for the notifications can be overrided
it with additional/alternative implementations).
The question was more about how the alerts/notification messages are raised - so instead
of the alert engine, it may be rtgov policies identifying a 'situation' an needing
to create an 'alert'. In this case, would rtgov use some form of client API to
report the alert, or simply create the alert and publish it on the bus?
Regards
Gary