[EMAIL PROTECTED] wrote:
Hi all,
I read some days ago, but didn't have enough time to react, that you are
wondering about don't use anymore things like Excalibur Cache in favor of
commons implementation.
Are you talking about removing the excalibur abstractions or just re-implement
them based on commons ???
Some things we already decided on. Excalibur Concurrent is replaced by
Doug Lea's util.concurrent library. Excalibur Collections is replaced
by Commons Collections.
There are other things that we are seriously contemplating, have almost
made the "do it" determination, but have not done it yet. THings like
Excalibur CLI being deprecated in favor of Commons CLI (which internally
speaking is much easier to understand). Also, Excalibur I18N in favor
of Commons Resource and Excalibur IO in favor of Commons IO. The thing
that is making us gun shy about the last two is that those are Commons
sandbox libraries.
We haven't made any determination regarding Cache or Pool as of this
time.
I ask this because i think this important to such abstractions in the components
repositories. In fact, imagine i implemented an application above Excalibur
Cache. What then if i need to switch to Turbine distributed cache ??? Without
Excalibur abstractions i can't do that. With them, i just have to implement a
new turbine-based component.
Right. Keep in mind that things that are proper components like Cache
and DataSource should be supported for a while. The class of libraries
that we are looking at deprecating are just that: libraries. They are
not abstractions or components, just libraries.
Avalon wants to get focused on their core competency, which is component
based development. Any libraries that might be used should be
maintained by a community that is focused on those libraries. It is the
only way we can continue to deliver top quality software to you guys.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
