On Thursday 16 October 2003 21:43, Stephen McConnell wrote:
> Recent updates to the Merlin platform in CVS include support for
> auto-decomissioning of components that are no longer referenced.
> The following log is a very simple demonstration testcase that
> creates a bunch of non-referenced components, invokes the garbage
> collector, and logs the resulting component decommissioning by
> Merlin.
>
>    [junit] Running playground.StandardTestCase
>    INFO   ] (testcase): Creating a bunch of hello instance
>    INFO   ] (template.hello): initialization as: 6829042
>    INFO   ] (template.hello): initialization as: 26030331
>    INFO   ] (template.hello): initialization as: 9089167
>    INFO   ] (template.hello): initialization as: 21860890
>    INFO   ] (template.hello): initialization as: 28517927
>    INFO   ] (testcase): running gc
>    INFO   ] (template.hello): disposal: 6829042
>    INFO   ] (template.hello): disposal: 26030331
>    INFO   ] (template.hello): disposal: 9089167
>    INFO   ] (template.hello): disposal: 21860890
>    INFO   ] (template.hello): disposal: 28517927
>    INFO   ] (testcase): gc done
>    [junit] Tests run: 1, Failures: 0, Errors: 0, Time elapsed: 2.109 sec
>
> Note that this is achieved *without* invoking release( object ).
>
> Am now looking into achiving the same thing with pooled objectes.

this is a *really* cool feature! I would qualify it as a quatum leap in merlin  
component manager history :))
thx a lot steve.
For some applications, it was really hard to invoke the release using the 
appropriate service manager. Having such feature will simplify a lot.

Does this means that you should set as deprecated the "release" method of 
service manager, since explicite release is not required any more?



---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to