avalon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Anton Tagunov <atagu...@mail.cnt.ru>
Subject Re[2]: Future Direction for Avalon
Date Tue, 13 May 2003 13:22:37 GMT
Hello, Leo and All!

>> From: Niclas Hedhman [mailto:niclas@hedhman.org]
>> Sharing of components between containers will introduce very 
>> interesting classloading issues, if you intend to support 
>> reloadable containers and/or components.

LS> Actually, I think the Fortress/ECM usage pattern ...
LS> .. for each component that is to be reloaded, we can block
LS> lookup()s and only allow release(). When all instances
LS> are released - reload.

Have been thinking much (webapp background) what if
 - old clients continue using the old class
 - new clients lookup and get instances of the new class?

As soon as the impl is reloaded and not the api it should be ok.

  I'm an outsider without proper understanding

- Anton

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

View raw message