The current implementation of zope.preference is quite specific to user preferences; however, it seems with a small amount of additional abstraction it could be generalized to support preferences across many contexts. Specifically, at a site or realm-level zope.preference could be leveraged to control configuration on the fly in a manageable way. Is generalizing this library beyond user preferences a reasonable extension?
The current implementation of zope.preference is quite specific to user preferences; however, it seems with a small amount of additional abstraction it could be generalized to support preferences across many contexts. Specifically, at a site or realm-level zope.preference could be leveraged to control configuration on the fly in a manageable way. Is generalizing this library beyond user preferences a reasonable extension?