Leo Simons wrote:
There's a simple choice:
either
* you restrict yourself to a subset of lifestyles that do not require
release() semantics (example: Phoenix, PicoContainer);
or
* you always do the release() semantics, even when they're not really
required
or, ...
You recognize that component creation, deployment, decommissioning and destruction are functional extensions of parallel notions present and applicable for objects - and you say to yourself - there is language that provides an object lifecycle model then encapsules the notion of memory management as part and intrinsic to the object lifecycle strategy - and that a component management model is intrinsically and extension of that abstraction and though this - embrace and leverage the notions and concepts of the underlying model.
From this - deliver a framework that reduces the number of lines of code - that is reliable and consistent. That ensures consistency, elimination of errors, frees the developer from platform concerns - and lets them focus on the real value.
Cheers, Stephen.
--
Stephen J. McConnell mailto:[EMAIL PROTECTED]
|------------------------------------------------| | Magic by Merlin | | Production by Avalon | | | | http://avalon.apache.org/merlin | | http://dpml.net/ | |------------------------------------------------|
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
