Thread:Talk:Echo (Notifications)/Registration with central service

Overall looking super great! :D

The main internals bit I'm still a bit unclear on is the bit about registration with the central service occuring 'on startup' -- since MediaWiki's execution model is mostly millions of short-lived processes, our only real 'startup' process is bootstrapping of the MediaWiki framework within a single web request or shell command...

ResourceLoader modules, for instance, are usually registered by dropping entries into a global array, which would be applied per-wiki, and that knowledge only exists within the given execution run.

If we need persistent, centralized retention, such as knowing which available event types exist throughout a large wiki farm so you can edit your delivery preferences, then we may need a different registration model that's more along the lines of setting up database tables, or interwiki links -- registration happens at upgrade/installation time, and stores data somewhere persistent (database).

Can we hammer down a bit what we think this'll take?