Nicola Ken Barozzi wrote: > IE (what I'd *strive* to do) > > Framework > | > | ------ Excalibur Fortress+Merlin+containerkit > | > | > Phoenix > | | | | | | | > Cornerstone, Phoenix Apps, Turbine services > > > The first step of all this is moving excalibur stuff in commons, as we > are currently doing. > In the meantime, finish the discussion about what we can do to make only > *one* framework implementation reference, based on Containerkit, > Fortress and Merlin. > If one size doesn't fit all, we will never go ahead ATM. > Finally concentrate on Phoenix and make it a real server killer app.
perhaps something like: ContainerKit: utilities for handling a component that is written according to the framework (lifecycle, metadata, maybe custom markers, etc.). Has a well defined API. Fortress: embeddable (extensible) container, based on ContainerKit. Adds features that are useful for a container but don't affect the writing of a component (e.g. pluggable component managers, locators, interceptors). Uses programmatic configuration and assembly. Has a well defined API. Phoenix: server killer app, based on fortress. Allows components to be configured and assembled via xml files without writing any code. [I don't know enough about Merlin to know where it would fit in] This linear dependence (Phoenix --> Fortress --> ContainerKit) allows the claim of *one* reference implementation while still providing Fortress to those who want to embed a container, and ContainerKit for testing/development environments etc. Note: the ContainerKit, being the core of the reference implementation, would be the /real/ implementation of the framework -- this is what you'd write the components for, and this is how you'd get the reusability -- the stuff in Fortress and Phoenix would be more for configuration and assembly. Finally, make the distinctions and dependancies between them *very* clear on the web site. Robert. P.S. it seems that most of my previous suggestions would go at the 'Fortress level' :) -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
