Guys,
I've recently started planning on using Avalon for my new server-side
project. To my surprise, reading information provided on the Avalon pages
left me more confused than I originally expected. :-) (This is not to say
that people are not doing a great job moving this project ahead.) Would
anyone be able to answer the following (maybe silly) questions?
1) To my understanding, Avalon has four higher-level containers: Merlin,
Phoenix, ECM & Fortress. Are ECM & Fortress better suited for embedded
server solutions? Consequently, are Merlin & Phoenix meant to be basis for
your stand-alone application servers?
2) Why is ECM being replaced by Fortress? Don't we still need a simple &
light-wait container/component manager along with sophistications of
Fortress?
3) Would using Fortress, as your container/component manager, exclude
wrapping your app up with Merlin or Phoenix?
3) Avalon's web documentation specifies that components are meant to
represent low-level application logic and blocks (implementing services)
are to encapsulate higher-level concepts, even at the utility level. Does
this mean that a good Avalon development practice requires us to put
components (wrapped up by some sort of manager) inside blocks that are, in
turn, managed by service manager(s)?
4) Is there a clear distinction between a component manager and service
manager?
5) One of the Avalon developers has recently said that "Avalon is about
doing things right not for a deadline". Wouldn't this mean that focusing
on a well-crafted kernel and plugable architecture should take precedence
over creating more containers and constantly improving things that are to
be deprecated?
6) Wouldn't focusing on creating a comprehensive project documentation
follow into "doing things right"? Updated and meaningful documentation
could not only create a happier Avalon community but also provide a clear
mission statement for project developers?
Thanks for your help. I hope that I didn't sound like a big complainer.
Pawel
American Express made the following
annotations on 12/08/2003 08:20:31 AM
------------------------------------------------------------------------------
******************************************************************************
"This message and any attachments are solely for the intended recipient and may
contain confidential or privileged information. If you are not the intended recipient,
any disclosure, copying, use, or distribution of the information included in this
message and any attachments is prohibited. If you have received this communication in
error, please notify us by reply e-mail and immediately and permanently delete this
message and any attachments. Thank you."
******************************************************************************
==============================================================================
