All,
i'm thinking about the following, can you give me
some feedback?
it seems services in Turbine are natural domain of
components. does it make sense to build Turbine on
or adopt some component framework like avalon ?
reasons:
1. life cycle
life cycle of services in turbine starts from
constructor and initiated by Turbine servlet. while
avalon provide life cycle on component and methods of
components which seem more granular.
2. service lookup.
in Turbine, use class name such as TurbineVelocity.handRequest(). in Avalon,
use ComponentManager for lookup. i personaly feel using
a manager can enable more sophisticated lookup impl,
e.g. get a component from a pool of that component type.
3. service management
it seems by using different roles, passing
configuration from framework to different components,
adopting some design patterns in avalon, it's easier to
manage components in avalon.
my 2 cents.
-sky
_________________________________________________________________
Get your FREE download of MSN Explorer at http://explorer.msn.com
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
