Sounds like a good plan, as another example, I really like the approach (n)hiberate has taken with their events and default implementations that make up the core of the framework and allowing users to override various parts
On Fri, Oct 3, 2008 at 11:49 PM, Ayende Rahien <[EMAIL PROTECTED]> wrote: > Recently I run into several cases where I wanted to be able to inject into > the container logic to decide how to deal with dependencies. > We already have the foundation in ISubDependencyResolver, but this is only > called for secondary dependnecies, for the root component, it is not > handled. > The extension point for this already exists (INamingSubsystem), but I think > that we can make it easier for users to deal with it by introducing a more > explicit extension point to deal with this scenario. > Thoughts? > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Castle Project Development List" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/castle-project-devel?hl=en -~----------~----~----~----~------~----~------~--~---
