Several components I am writing have a unified access class that sublets it's actions to a set of providers. Example:
AuthLogic might simultaneously have an HTTPProvider, SQLProvider, and LDAPProvider. AuthLogic is responsible for directing auth requests to the appropriate provider and returning a response. Ideally each provider would have a full component lifecycle. Currently AuthLogic is acting as a sort of pseudocontainer, wherein it provides a partial lifecycle (partial meaning a subset of it's own lifecycle). Preferable Merlin would be used to load/manage these providers. I know I can declare each provider and then tell AuthLogic which components to hunt down. I dislike this methodology as it seems clunky at best, confusing and hard to manage at worst. Would it be appropriate/possible to upgrade AuthLogic from a component to a custom container. I am considering this 'upgrade' for several components. What negative effects would such an action have on future development. Corey -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
