i.e. Child.ForName(“subscriber”) roughly equates to “give me child of the one named subscriber (SubscriberInfo?)

Are Child.ForName, .Eq, Attrib.ForName MicroKernel Registration API extension methods?

Sorry about the dumb questions. I am deciding on IoC containers and evaluating code-based configuration paradigms. I think I understand how to leverage your approach on down the road – I thought I might as well poke the unknowns. I am also a little linq-naive.

Just few a questions in regard to the class encapsulation where Subscriber encapsulates SubscriberInfo. I typically warn myself off of usage like this because I don’t understand the qualities.

Is this implementation:
a) a pattern of which I am unaware
b) Does it afford quality to the container or the fluency framework?
c)?

Thanks, Brad

Component.For()
.ImplementedBy () .Subscribers(Subscriber.ForComponent (“subscriberId”,(x, y) => x.ServiceStarted += y.Subscriber));

This is possible since I’m using lambda’s as delegates. I think i can process it to get the right stuff: which subscribed to what but this ForComponent part disturbs me as it is not necessary.