> From: Stephen McConnell [mailto:[EMAIL PROTECTED]] > > Berin Loritsch wrote: > > > >BTW, What is your feeling on lifecycle extension? Is it > something that > >we can propose for ContainerKit > > > > I'll have to dig before given you an opinion.
Cool. I would say check out the docs online, but it seems I have to add a link for the missing page.... The xdocs do have the latest. I'll see what I can do to get the new page published ASAP. > >and make it easier for all containers > >to support it? Stephen, what is your feeling on it? > > > > I would like explore a Merlin/Fortress merger. Merlin content on the > Kernel/Container/Meta-Data layers, Fortress content on the handlers, > lifecycle extensions and probably more that I'm not up to speed with > yet. There's stuff in-between that would need discussion > simply to get > a better picture of where the boundaries and relationships are. > > Thoughts ? I agree. Hmmm. Merlin's Fortress.... Here is my understanding of the differences (I am sure there is more): * Fortress uses MPool and Event so that we have asyncronous management. Critical path is not bogged down with management functions, and pooling does not require the Pool interface. * Merlin has the better metadata model. Fortress accomplishes the same thing from the RoleManager--however it is more limited. * Fortress provides a more direct conversion from ECM world due to the integration of the Component/Service Selector interface. Fortress takes advantage of the posted "best practices" which you don't agree with ;P and any role that ends with "Selector" gets the ***Selector returned. The migration path is so that components that do not expect a ****Selector path can still coexist by using the default implementation. * Fortress has the Handler classes and support for four different handler types--although I would like to see the pure factory (i.e. no reuse) handler to be deprecated and serious warnings to be posted if it is used. Any component that requires its use is poorly designed. * Fortress has initial experimental support for integration with the Excalibur instrumentation packages. I don't know about Merlin. * Fortress has the initial experimental support for extendable lifecycles. It should be easy to integrate with Merlin, et. al. Please excuse my ignorance of Merlin. > > Just for reference, I've updated a lot of the documentation > on Merlin so > getting a better idea of how Merlin is doing its stuff should > be easier. > http://home.osm.net/doc/merlin Cheers, Steve. > > > >-- >To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> >For additional commands, e-mail: ><mailto:[EMAIL PROTECTED]> > > > -- Stephen J. McConnell OSM SARL digital products for a global economy mailto:[EMAIL PROTECTED] http://www.osm.net -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]> -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
