-----Mensagem original----- De: Berin Loritsch [mailto:[EMAIL PROTECTED]
> Check out the Directed Acyclic Graph utilities in Fortress > (**.fortress.**.dag). Porting that to C# will help you find > violations of the first guideline, as well as help you order > your dependencies so that they are loaded and disposed of in > the proper order. Humm.. I'll do it tonight. But, before that, what is the meaning of loading a dependent component? It will be made available through look ups anyway, right? Maybe dependencies handling are a Java issue, where the order of class loading is a important issue. We won't have this kind of problem in .net. At least while we don't support a kind a hot deployment. > > by using a LifestyleManager to centralize invocation of lifestyle > > methods. > > > Lifestyle is more like "transient", "singleton", "pooled", etc. > Lifecycle is the initialization, destruction, etc. I'll change its name tonight ;-) hammett --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
