+1 from me, then.
On Fri, Oct 3, 2008 at 6:15 PM, Ayende Rahien <[EMAIL PROTECTED]> wrote:
> No, the naming system itself.
> It will allow extension similar to this:
> public interface IDependencySelector
> {
> IHandler Select(Type type, IEnumerable<IHandler> handlers);
> }
>
>
> On Sat, Oct 4, 2008 at 4:10 AM, hammett <[EMAIL PROTECTED]> wrote:
>>
>> What's on your mind? Something in between the kernel and the handlers,
>> but before the naming subsystem?
>>
>> On Fri, Oct 3, 2008 at 2: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?
>> > >
>> >
>>
>>
>>
>> --
>> Cheers,
>> hammett
>> http://hammett.castleproject.org/
>>
>>
>
>
> >
>
--
Cheers,
hammett
http://hammett.castleproject.org/
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---
