We consider how custom events and their users should be identified and maintained in the presence of dynamic reconfiguration.
We would like to provide similar mechanisms to both client and server-side plugins and expect some interoperation. We recognize that these are substantially different environments.
Historic Custom Events mostly propagating data related updates such as scrubbing through datasets.
Timer Logic where timer events are scheduled and maintained server-side for data collection.
Service Logic where our timer experience is generalized slightly for monitoring and alerting applications.
Wiki Events where we propose mechanics of addressing and reconfiguring server, client and server-to-client event in light of recent prototypes.
aspirational documents
lifetimes on client and server
headless clients
start/stop configuration logic
drag/drop configuration logic
collaborative events