"Quinton McCombs" <[EMAIL PROTECTED]> writes:
>I would say not to create them at all. As people migrate to the fulcrum
>services that they can obtain an instance of the component from a container
>and give it back to the container when they are done with it.
>Granted, you can get away with using the fasade classes in cases where the
>contain is using a singleton approach for creating instances of the
>component. Otherwise you must either release the component (losing state)
>after each method call of the fasade class or don't worry about releasing
>them (memory leaks).
The static facades are something that work well with the current Turbine
structure. I'd definitely see them go in an avalon based Turbine, mainly
because using static accessors simply isn't avalon style.
Regards
Henning
--
Dipl.-Inf. (Univ.) Henning P. Schmiedehausen INTERMETA GmbH
[EMAIL PROTECTED] +49 9131 50 654 0 http://www.intermeta.de/
Java, perl, Solaris, Linux, xSP Consulting, Web Services
freelance consultant -- Jakarta Turbine Development -- hero for hire
"Dominate!! Dominate!! Eat your young and aggregate! I have grotty silicon!"
-- AOL CD when played backwards (User Friendly - 200-10-15)
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
