avalon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Leo Sutic" <leo.su...@inspireinfrastructure.com>
Subject RE: [merlin] auto-decommissioning
Date Sat, 18 Oct 2003 09:19:04 GMT

> From: Stephen McConnell [mailto:mcconnell@apache.org] 
> The potential issue here (that we discussed way back) 
> concerns the fact that a component lifestyle is not assured.  
> So basically the consuming component does not know if service 
> implementation is pooled or not - and as such, non-release 
> of a component could lead to a breakdown because the pool 
> capacity reaches a maximum. 
> There are two aspects which I think change this conclusion ...
>   (a) the notion of active versus passive release
>   (b) the ability of a pool implementation to partitipate in
>       passive decommissioning when required

But how does this change the conclusion that active release is
always safe, and passive release is potentially unsafe, and that
the guideline therefore is "always active release"?


To unsubscribe, e-mail: dev-unsubscribe@avalon.apache.org
For additional commands, e-mail: dev-help@avalon.apache.org

View raw message