#6 Persistence service

[Anonymous]

Some things, like a category manager, would profit from having access to a persistence service to keep the category mappings from run to run, and a dynamic loader, to keep the component to shared object file mapping information (instead of rediscovering everything at every program start).

Doing this properly might be more or less complicated. For example, should a such a persistence service also keep configuration information, such as the infamous Windows registry? I think that for things such as the dynamic loader, it should only be a cache to improve performance (deleting the persistent information would only result in the dynamic loader needing to redetect all the components).