Mailing-List: contact avalon-dev-help@jakarta.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Avalon Developers List" <avalon-dev@jakarta.apache.org>
Reply-To: <bloritsch@citi-us.com>
From: "Berin Loritsch" <bloritsch@citi-us.com>
To: "'Avalon Developers List'" <avalon-dev@jakarta.apache.org>
Subject: RE: Context: usage recommendations? ( Re: [SUMMARY] Context )
Date: Tue, 3 Dec 2002 09:30:49 -0500
Message-ID: <000501c29ad8$93d8d630$2100a8c0@acsdom1.citius.com>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
Importance: Normal
In-Reply-To: <200212040135.37463.peter@realityforge.org>

> From: Peter Donald [mailto:peter@realityforge.org]
> 
> On Wed, 4 Dec 2002 00:16, Berin Loritsch wrote:
> > >  - access to proxying/interceptor chains for current 
> block and ability
> > >    to construct new chains for objects you want to pass around
> > >
> > :/  Just make it a decent library.
> 
> That will happen anyways but that has little to do with what 
> I am talking 
> about. A block has to have access to the current runtime 
> state of the chain 
> and has to be able to bind components to existing chains to 
> maintain the 
> correct isolation contexts. Have a look at how HPs CSF does 
> it and more 
> importantly their documentation on why they do it. 


Link?

And I fail to see why we can't have stuff like that handled
for us automatically....

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