avalon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Niclas Hedhman <nic...@hedhman.org>
Subject Re: Future Direction for Avalon
Date Wed, 14 May 2003 18:52:17 GMT
On Tuesday 13 May 2003 05:22 am, Anton Tagunov wrote:
> 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?

This may not be good enough, since the "old client" may be a never-stopping 
application, but that needs the upgraded service.

I think 2 things is required;
1. A defined "availability (notification) protocol", which is the underlying 
driving mechanism for making services available or not.

2. A higher level system (someone called it interceptors) that understands the 
availability protocol, and makes it easy for the "client" to access the 
service, without worrying about the "availability (notification) protocol".


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

View raw message