On Mon, 2003-01-27 at 08:09, Leandro Rodrigo Saad Cruz wrote: > On Sun, 2003-01-26 at 16:20, Quinton McCombs wrote: > > I would like to propose that we drop stop using the strutum lifecyle > > interfaces altogether in favor of Avalon's interfaces. > > +++++1 > > > > > Fulcrum currently has it's own ECM that is used load load it's services. > > This can still remain in place. When a service is loaded from within > > Turbine, the request would go to Turbine's instance of the ECM. If > > there is no component loaded with Turbine's ECM that matched the role, > > the request would be passed to Fulcrum's ECM. > > Why not use only one container ?
+1 > > > > I think that this can be done without affecting the way that services > > are used within Turbine. We can still keep the abstract classes with > > static methods that we have in place right now. They will simply pass > > the request to obtain a reference to the service to Turbine's ECM. > > I think this static accessor should be dropped ! We should use component > composition instead ! +1 The static accessors should be dropped ASAP. -- jvz. Jason van Zyl [EMAIL PROTECTED] http://tambora.zenplex.org In short, man creates for himself a new religion of a rational and technical order to justify his work and to be justified in it. -- Jacques Ellul, The Technological Society -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
