Stephen McConnell wrote:
> Isn't this more about communication. One of the things the article
> talks about is "keep-it-simple-stupid". One of the *really* nice
> things about the Avalon framework is that it is *really* simple.
> Ok, so keeping it simple also means we don't get into heavy weight
> stuff at the framework level - but the feature list for a framework
> (such as JNDI and JDBC etc.) are more than the Avalon framework, and
> more-than/less-that Excalibur. My feeling is that to move from
> "something-to-watch" to "don't-live-without" we need a couple of
> additional ingredients:
>
> a) Phoenix with upgrade for
> "stupid-user-like-me-doesn't-need-to-think" deployment
> model
>
> b) phoenix upgrade to beta release
>
> c) Excalibur components/service framework for easy JNDI
> and JDBC + full integration of these features as Phoenix
> core services (like logging) - its there and your don't
> need to think about it (a.k.a. default Phoenix configuration).
>
> d) Marketing push that positions Phoenix as (a) the Avalon app
> server, and (b) as the Avalon framework reference
> implementation and .
This will get a big push when my book is done....
--
"They that give up essential liberty to obtain a little temporary safety
deserve neither liberty nor safety."
- Benjamin Franklin
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
