Hi, As some, or all, of you know I posted a little message on the Avalon list about some Turbine/Avalon cooperation. After asking a few of the developers in IRC I decided that it would probably be a waste of time to try and roll another component framework which is what stratum will evolve into if we keep going. We need what Avalon provides and we'll get something more robust and working faster by cooperating with the Avalon folk.
Vincent Massol was the one who finally convinced me with a few conversations and some example code. He's found Avalon to be quite light weight and hasn't had any reliability problems. He is really a user of Avalon and isn't an Avalon committer even though he has now had extensive experience with Avalon. Overall he's had good experiences and I value and respect his opinion on the matter. So I don't really want to pursue our own path when it comes to a component framework, I think we should migrate what we've done with stratum, which is very little anyway, and fulcrum to Avalon and leverage the work they've already done. I think the Avalon community is quite willing to help us too. Berin and Leo have offered some sound advice and I think they can help us get up and running if we decide to move toward using Avalon. There were a few people in IRC who raised some concerns about the mode in which Avalon works which is that all components live inside a container. The concerned just wanted to make sure that a Turbine app could still be packaged up in a WAR file and be dropped in a servlet container. This is certainly possible and is what Cocoon does. I am interested in the 'life is in the container' mode but both are possible as both modes are currently in practice. So I think this is good news and I hope it sparks some discussion. -- jvz. Jason van Zyl [EMAIL PROTECTED] http://tambora.zenplex.org -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
