On Wed, 13 Nov 2002 10:29, Clemens Marschner wrote:
> Do you think one should apply the general pattern that interfacing to the
> Avalon framework is only done on top of a system that is able to run
> without Avalon, or to use Avalon as a framework that everything else is
> built on? I think we are at a point where we design a new system and make
> only code reuse where it is applicable.
Either is possible and different situations call for different approaches.
Personally I try to keep all of my code as lightly coupled as possible. Which
means I tend to have an Avalon independent part and an Avalon specific part.
However sometimes you will find your self recreating different parts of the
Avalon lifecycle. ie You will have a custom lifecycle for your apps or custom
configuration/whatever - in which case I would highly recomend you move to
Avalon.
It all comes down to how fine grain you want your pluggability /
componentization. The more fine grain you go the more likely you want to use
Avalon for the low level stuff.
I am not sure thats much of an answer though ;)
--
Cheers,
Peter Donald
Sufficiently advanced science is
indistinguishable from magic"
-- Arthur C. Clarke
--
To unsubscribe, e-mail: <mailto:avalon-users-unsubscribe@;jakarta.apache.org>
For additional commands, e-mail: <mailto:avalon-users-help@;jakarta.apache.org>
