> Next step will be Turbine 3.0 > decoupled Torque > support for OJB included > coupled Fulcrum and services deprecated (for backward > compatibility) > Plexus container for the components > Components migrated from decoupled Fulcrum > other Avalon components can also be used in Turbine and vice
This renumbering seems reasonable to me, however (and you might have been thinking this, it is not contrary to the above) I would like for turbine 3 not to depend on anything in fulcrum, even though it will still be able to init any fulcrum services a users application might have. The services T3 owns (Pull, RunData) and depends directly on (the whole TemplateEngineService clusterfsck, possibly others...) should be recast as components, or replaced with better mechanisms (particularly in the case of TES -- we can do better =) That is what I've been thinking at least, and I _think_ it is mostly aligned with what Jason wants / needs. -- jt -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
