I am back, and after only a week being on vacation I was greeted with
1287
emails. I take that back, that's 1287 + 1294 + 596 because that's all
my
email client would download at one time. Because of that, I am going to
have to reduce the number of lists I am subscribed to. (Like Axis, I
started
to work with them, and never could get back).
Anyway,with a couple hundred emails in just Avalon-Dev the one project I
am
most interested in, there were a few topics that saw a lot of action.
We
have the "One Container" thread, and it's corrolary "Three Containers".
I couldn't hope to keep up with everything (I have to work for a living
as
well).
My spin:
One spec, many containers. Just like J2EE. Coming up with a spec is
not
easy. However, we have to write what we know. The meta data stuff
being
written in Merlin is great, I like it. Fortress has a lot going for it,
and I want to make it easier to work with (both to maintain and to use).
If Marcus made his commit, it has an extensible lifecycle without too
much
introspection. So we have a foundation to work with other aspects of
components such as persistence of configuration changes and the
component's
working set of data. Bottom line, each of the containers we have has a
specific set of plusses and minusses.
If you are planning a J2EE project, you don't just go out and buy a BEA
server. At ~$16,000 per CPU licensing fees, it seems rediculous to buy
one of those to only service 25 users. You have to size your server for
your project.
In Avalon, you have the concept of the embedded server and the
stand-alone
server.
Anyway, I am still catching up, so if anyone can help me cut through the
crap and get me up to speed with the current understanding, I would
definitely appreciate it.
"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]>
