Server events path in API

[VladimirKalachikhin]

As far as I understand, no any path in API with server events?
Case:
The Webapp with configuration via server plugin.
User change plugin settings in Admin -> Plugin Config.
Ok, Plugin stopped - Plugin started.
But the webapp no have info about change of plugin status. So, the webapp continues to work with the old parameters.

Of course, I can create my own path for this case, but may be a centralized source of information be more convenient?

[tkurki]

I think this is a great idea and use case and perfectly doable!

I think this should be opt-in, so that a plugin could tell the server that "hey, i want my configuration changes to be available over WebSocket". Some plugin's configuration is not relevant for anything but the plugin and some include sensitive data, like credentials to remote services, that we probably don't want broadcast to everybody.

[VladimirKalachikhin]

I don't think it should be passed configuration itself. The event is enough. Does the webapp somehow get the configuration at startup? Well, let him reload window himself by event "plugin start".
I think the following events would be helpful:
plugin start / stop
metainfo changed
path appeared / disappeared
data source appeared / disappeared ?
errors ?

It would be nice to have access to the configuration too, but this is different.