> I am not sure that it would be great to require Phoenix for tubine at this > stage - mainly as it is aimed at standalone servers at this stage. However I > am currently refactoring it so that I can extract a generic ServiceKernel > that allows you build a Phoenix-like Container (ie uses something equivelent > to BlockInfo but more generic) simply.
This sounds really interesting. One of the points of interest / confusion for us is whether turbine would need to be bootstrapped by something else or whether it could _be_ the container as in the current model. If we can gradually move toward encapsulating all our services as Avalon-Framework components, but still keep the turbine servlet at the top I think that will alleviate a lot of concerns. Not to say that I am opposed to having turbine managed by something else (Phoenix I believe?), only that it gives us less we _have_ to do right away. I'm just getting my head around all this though, so maybe I'm way off base. > My main aim is to create something useful for all the containers (and more > specifically Myrmidons at this stage). I'm going to start lobbying Leo to use > it in fortress and that way services will be transportable between all > containers with no hassles. > > However programming to this container would mean you could transport between > all the containers with zero hassles. Just need to write the container > specific assembly/config file and away you go! -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
