Serge Knystautas wrote:
Harmeet Bedi wrote:
[...]
- Move away from Avalon/Phoenix. There has been some talk on this topic. WeI've been as guilty as anybody of getting frustrated with certain parts of Avalon, and then condemning the whole lot. There's plenty of good there, and I think there are parts where we need to take ownership of the implementations because they are so key to James. We've relied probably way too long on the file stream implementation for the file message store, and the thread management/object pooling/connection pooling and other pieces might be better to build in the James codebase. As Steve just added, the design gives us the liberty to choose, and we (I) should do a better job appreciating that.
could keep the framework part and not use Phoenix if this is a sensible
goal.
Good words :-)
Just speaking philosophically (and not about any particular decision), what do people think of this approach: when we hit a piece of the Avalon codebase (framework, excalibur, what-have-you) that we're unhappy with, then we make a copy of it, possibly even repackage it, add it to James, and make the code work for our needs. Often we will know a small piece is not working, but may not know the perfect solution until we use it in James for a while (a few test runs, maybe a few months). I think we would benefit by not getting (feeling) stuck waiting for an Avalon release, and the Avalon projects would benefit with more people building components. This can be done as healthy competition, and if we ultimately figure a better way to build a component, we can certainly pass it back to Avalon's codebase.Geem this is one of the *best* mails about using Avalon that I've read so far!
My compliments :-)
One note: I've understood the difficulty developers had with relying on Avalon code you don't have direct access to.
I felt the pain.
That's why I have proposed to Turbine, Avalon and Apache Commons that we create a common repository of Avalon components on Apache Commons, where all involved projects can actively partecipate on.
It will take months maybe, but it has had a good acceptance :-)
In the meantime, the above proposal is excellent; Peter Donald has also said that we could give commit access to developers on components they need to work on even now, and I second it, so in case you really need it, don't hesitate to make yourselves heard.
Thank you all, and VIVA JAMES! :-D
<shameless-plug>
BTW, wanna make the site using Forrest? It would make a nifty pair with the new logo ;-)
</shameless-plug>
--
Nicola Ken Barozzi [EMAIL PROTECTED]
- verba volant, scripta manent -
(discussions get forgotten, just code remains)
---------------------------------------------------------------------
--
To unsubscribe, e-mail: <mailto:james-dev-unsubscribe@;jakarta.apache.org>
For additional commands, e-mail: <mailto:james-dev-help@;jakarta.apache.org>
