Leo Sutic wrote: > > Now, I'm also considering porting Cocoon to this new > wonderful architecture, if it turns out as great as I expect it to. > Would the Cocoon community consider accepting such a port? > Yes, we would definitly consider it, but of course it could turn out that we don't accept it. If you're really planning to do this, I think the best thing to do is to ask beforehand at cocoon dev, what the Cocoon community thinks about it. The key point for me personally (so, I'm not speaking for the whole Cocoon community) is if such a move has advantages over the current solution. The current ECM solution is working pretty well and is very easy to understand. We hoped with the move to Fortress that things even get easier/simpler but this currently not true. But as the move isn't finished yet, it's not fair to judge right now.
Now, the other interesting point for me, is compatibility with other container frameworks. As far as I know, most other containers are somehow compatible with Avalon - at least they can run Avalon components. But I currently don't see the other direction. But I have some minor improvements for Fortress on the table that I want to implement in the next weeks. Carsten --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
